> The rust compiler is amazing. The error messages it provides are clear and helpful
I'm sure that Clang inspired the great error messages - it sets a very high bar for new compilers (and old - GCC is still catching up).
> Being a Windows dev by day I do bemoan the fact that this platform is a bit .. behind
I'm sure that once 1.0 is released there will be a greater effort to make the Windows experience more seamless. This will be extremely important if we want to convince more game developers to give Rust a go. Have you seen https://github.com/PistonDevelopers/VisualRust/?
That said, IDE support isn't exactly what I was referring to.
- you need to install mingw separately and there are lots of reports about conflicts with other software that might bundle a different version of mingw
- installing cargo is weird (so far .. I failed and don't use it)
And even with my first baby-steps (i.e. doing basically nothing of value) I discovered some limitations, one being that you cannot create a DLL that exports an unmangled entry point - for stdcall (other calling conventions don't have that issue and follow #[no_mangle] or #[export_name="foo"].
BUT that's really not a huge deal for me. Just a bumpy road at times.
I'm sure that Clang inspired the great error messages - it sets a very high bar for new compilers (and old - GCC is still catching up).
> Being a Windows dev by day I do bemoan the fact that this platform is a bit .. behind
I'm sure that once 1.0 is released there will be a greater effort to make the Windows experience more seamless. This will be extremely important if we want to convince more game developers to give Rust a go. Have you seen https://github.com/PistonDevelopers/VisualRust/?