You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(This is more food for thought)
It seems like there is a big porosity between the C, C++ and Rust ecosystem nowadays; and even in term of underlying tools technology (debugger, LSP seem common to CDT and ShellWax...). Would it make sense to include Eclipse Corrosion into the C/C++ package to let its developers more easily adopt Rust (as some companies such as Microsoft have started to do on some of their products)?
The text was updated successfully, but these errors were encountered:
It may be a good idea. IIRC Corrosion uses LSP and DAP? As CDT is moving to using LSP (but not DAP though) the alignment becomes a little easier. I have raised eclipse-cdt/cdt#949 so the CDT community knows about this too.
We discussed this at the most recent CDT call - eclipse-cdt/cdt#967 - and the conclusion was "supporting Rust sounds like a good idea, when we get an owner to support ongoing Rust work we should revisit again"
(This is more food for thought)
It seems like there is a big porosity between the C, C++ and Rust ecosystem nowadays; and even in term of underlying tools technology (debugger, LSP seem common to CDT and ShellWax...). Would it make sense to include Eclipse Corrosion into the C/C++ package to let its developers more easily adopt Rust (as some companies such as Microsoft have started to do on some of their products)?
The text was updated successfully, but these errors were encountered: