Pure design questions are off-topic for Code Review. And importantly, no matter how much code you include, a question about designing a language can't possibly be on-topic for Code Review.

Code Review requires real, working code.

If there is nothing to interpret/compile the code, the code can't be real or working. Your language is nothing more than a special syntax for pseudo-code.

If there are still design questions for the language (or what an upcoming version of the language might look like), those design aspects can't possibly be already implemented in an interpreter/compiler.

Theoretically, once you get an interpreter/compiler going, you could sort of cheat the system slightly by posting some code written in your language for you review and appending something like:

Oh by the way, I'm the language designer, so any critique of the language syntax or mechanics would be appreciated as well.

But you'd have to be careful with this. If this is the core of your question, I'd be likely to vote to close.

Questions about design in general, and designing a language in specific, can be potentially on topic on Programmers, but of course, don't take my word for it, read their help center and visit their meta.

Pure design questions are off-topic for Code Review. And importantly, no matter how much code you include, a question about designing a language can't possibly be on-topic for Code Review.

Code Review requires real, working code.

If there is nothing to interpret/compile the code, the code can't be real or working. Your language is nothing more than a special syntax for pseudo-code.

If there are still design questions for the language (or what an upcoming version of the language might look like), those design aspects can't possibly be already implemented in an interpreter/compiler.

Theoretically, once you get an interpreter/compiler going, you could sort of cheat the system slightly by posting some code written in your language for you review and appending something like:

Oh by the way, I'm the language designer, so any critique of the language syntax or mechanics would be appreciated as well.

But you'd have to be careful with this. If this is the core of your question, I'd be likely to vote to close.

Questions about design in general, and designing a language in specific, can be potentially on topic on Programmers, but of course, don't take my word for it, read their help center and visit their meta.

Pure design questions are off-topic for Code Review. And importantly, no matter how much code you include, a question about designing a language can't possibly be on-topic for Code Review.

Code Review requires real, working code.

If there is nothing to interpret/compile the code, the code can't be real or working. Your language is nothing more than a special syntax for pseudo-code.

If there are still design questions for the language (or what an upcoming version of the language), those design aspects can't possibly be already implemented in an interpreter/compiler.

Theoretically, once you get an interpreter/compiler going, you could sort of cheat the system slightly by posting some code written in your language for you review and appending something like:

Oh by the way, I'm the language designer, so any critique of the language syntax or mechanics would be appreciated as well.

But you'd have to be careful with this. If this is the core of your question, I'd be likely to vote to close.

Questions about design in general, and designing a language in specific, can be potentially on topic on Programmers, but of course, don't take my word for it, read their help center and visit their meta.

Pure design questions are off-topic for Code Review. And importantly, no matter how much code you include, a question about designing a language can't possibly be on-topic for Code Review.

Code Review requires real, working code.

If there is nothing to interpret/compile the code, the code can't be real or working. Your language is nothing more than a special syntax for pseudo-code.

If there are still design questions for the language (or what an upcoming version of the language might look like), those design aspects can't possibly be already implemented in an interpreter/compiler.

Theoretically, once you get an interpreter/compiler going, you could sort of cheat the system slightly by posting some code written in your language for you review and appending something like:

Oh by the way, I'm the language designer, so any critique of the language syntax or mechanics would be appreciated as well.

But you'd have to be careful with this. If this is the core of your question, I'd be likely to vote to close.

Questions about design in general, and designing a language in specific, can be potentially on topic on Programmers, but of course, don't take my word for it, read their help center and visit their meta.