| ▲ | onlyrealcuzzo 4 hours ago | |
> Having the result type of a function change based on context sounds like a horrible idea because it would introduce tons of unnecessary ambiguity. I think you're assuming the language won't warn you if you're doing something cost ineffective, and that there aren't modes to compilation which will make you make things explicit whenever its ambiguous. For a person to get started, they should be able to compile in `easy` mode and do things that make sense to them, and the compiler should only bitch at you to be pedantic when you ask for that. Especially because an LLM can probably do that pedantic part for you. You: write code almost as high level as a scripting language, it works, turn on strict mode, most of the time you get auto-fix solutions/options from the compiler. That's my opinion anyhow. I assume most Rust people won't like it. That's fine. You already have your language! I'm not trying to make a slightly different Rust for Rust people... I'm trying to make Rust more accessible to everyone else. | ||