You'd expect people to code in a language they likely have never seen before in an interview? Would you provide the documentation?

People have different opinions, and all can be fine, I don't claim to have the definite answer.

IMHO coding is about thinking, not about the knowledge of a programming language. How do you split the problem into smaller problems? And then in even smaller ones to the level you can express solutons in code? Then what can be abstracted for future changes?

I would not provide documentation, but explain how the candidate can write some code if they tell me what they want to do, perhaps write the code sketch for them.

The language is so simple that any candidate can get the basics in a few minutes. And I'm interested in their thinking, not in their mastery of a programming language. If you're a good Python coder, I'd also hire you for writing Go.

(To understand where I came from: This is perhaps from my personal background, I have done hundreds of interviews, I wrote code in 20+ languages and was paid for in 10+ languages over the last four decades. So I value thinking and problem solving more than the correct syntax in an interview - e.g. if you write Java code, I don't care about braces and semicolons)

I agree coding is about thinking. I've worked for Apple, and written a GOTY game, but I don't know how I'd react if asked to write code in such an esoteric system. I could talk through the concepts, and you could write the code. Cheers!

Then perhaps we don't fit each other, which is fine, and isn't finding that out a good result of an inteview (that you don't want to work with me? - instead of starting and then beeing unhappy - IMHO not enough candidates evaluate the company and their future manager in interviews)