[record_use] Completeness: enum value usages

[dcharkes]

enum value usages (I don't know if this is possible, because idk. if unused enum values are even tree-shaken)

#2902

They'd work in a similar way to const instances.

[DPrakashhh]

Hi @dcharkes, I just finished the Swift2ObjC default params task—all 70 tests are passing now!

I’ve been following the 10+ new issues you opened for record_use and find the 'Completeness' work very interesting. As a second-year student, what should I study to be helpful here? I’d love to contribute if there’s a good entry-level issue!

[dcharkes]

@DPrakashhh These are all fairly difficult tasks that require a deep understanding of the compiler and the programming language. (1) They all need to be implemented in the Dart SDK in the various compilers: the dart2js compiler, the native compiler, and the wasm compiler, and (2) they all require reasoning through all the corner cases to ensure we ship something that is consistent and reliable. (I'm going to have to do significant investigations and analysis in order to understand what's feasible etc. So I might as well do those changes then as well. Probably 80% of the time is going to be thinking/reverse engineering/designing and only 20% writing the code.)

Contributing to the objective C, Swift, Java and Kotlin interop is more accessible because these are packages. These of course still require reasoning through all the combinations that the language features of these languages interact with each other and the Dart code our interop packages generate. But they don't require understanding the internals of the Dart compilers. So, I'd focus on contributing on those.

P.S. Thanks for contributing! I love the energy! 🚀

[DPrakashhh]

Thanks for the advice. I will stick to interop. Are there any other 'SwiftGen MVP' tasks I can take on? I am aiming for GSoC 2026 and want to keep contributing here to build up the necessary skills.

[dcharkes]

You can work with @liamappelbe on landing #2910 and he can direct you for things to work on.

P.S. I'll mark these notes as off-topic here because they're not really about this GitHub issue.