3 ms·
> so long as the global usings are only kept to a single file Here's where the mess starts. It seems far too easy to sneak a global import statement in to ran
by t-writescode 5y ago
> so long as the global usings are only kept to a single file
Here's where the mess starts.
It seems far too easy to sneak a global import statement in to random files and then have the entire codebase polluted by it.
I feel like this is too foot-gun'y, myself.
- Akronymus 5y agoYeah, there should definitely be a way to have the compiler enforce global usings in only a specific file.