> What you're seeing there is actually validation :), the lat/lng type is not magically inferred but instead explicitly requested by the code - if it were not valid it would generate a user-friendly, localized error message. Also the underlying document hierarchy that holds the data is validated. So on the contrary it is actually hard not to validate content in eno.

Please make this clear on the website! I think it’s a clever idea.

Also, this has garnered some attention on Lobste.rs [1], if you’re interested to read the discussion there as well.

[1]: https://lobste.rs/s/jno6gb/eno_notation_language_libraries