Support Rust 2024 #382
Support Rust 2024 #382
Conversation
edition 2024 doesn't allow specifying `ref` redundantly, so instead of specifying `ref`, use `as_ref()` or `&` to ensure the thing being matched is a shared reference type
2015 doesn't work because the old `extern crate` syntax is required to be generated for that, so I assume it's never worked with bebop
|
Thanks for the fix! I'm happy to merge this as-is if it's blocking you, but wanted to mention we're in the middle of the 2026 edition rewrite over at https://github.com/6over3/bebop-next — new compiler backend, grammar, the works. If you're up for it, you contribute a Rust plugin and runtime for the new compiler. The benefit of the new architecture is you can write the code generator and runtime in Rust, rather than C#. We're offering small bounties and would really appreciate the feedback from someone actively working with Rust. No pressure though — just let me know which direction works best for you. |
|
Short term, I'd like to have this fix since having MSBuild generate C#/Rust/TypeScript actually fits into my existing workflow well. I'd be happy to follow along with your progress and give feedback/contributions where I can! Do you have some place that development discussion happens? |
2 participants
Resolves #372
See https://doc.rust-lang.org/nightly/edition-guide/rust-2024/match-ergonomics.html for the Rust edition 2024 breaking change this PR addresses