In the current scenario, where the definition of 'Rust' changes on a daily basis, that's a major pain-point, but once Rust hits 1.0 then ...

In the current scenario, where the definition of 'Rust' changes on a daily basis, that's a major pain-point, but once Rust hits 1.0 then all future changes will be backwards-compatible (until version 2.0, in the distant future if ever), so it should be much less of an issue. That said, it's definitely a thing the Cargo devs are thinking about: https://github.com/rust-lang/cargo/issues/1044 https://github.com/rust-lang/cargo/issues/837

Comments (0)

No comments yet. Start the discussion.

In the current scenario, where the definition of 'Rust' changes on a daily basis, that's a major pain-point, but once Rust hits 1.0 then ...

Tags

Related issues

I guarantee it's a convenience feature.

That isn't really relevant for the tool starting the container.

Why is there no link to the source?

Something I wonder about in this domain is if this is the fault of the language.

Namespace pollution is an annoying problem in Rust.

Currently, no language ports of Timefold Solver are planned.

I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...

Why is there no simple workaround for this?

In the current scenario, where the definition of 'Rust' changes on a daily basis, that's a major pain-point, but once Rust hits 1.0 then ...

Comments (0)