4 ms·

There's actually several features here that could radically change the way I structure certain types of code -- notably async streams and default implementation

There's actually several features here that could radically change the way I structure certain types of code -- notably async streams and default implementations, in addition to nullable reference types -- and it will be hard not too look at the older methods as legacy. These changes will have a comparable effect to what LINQ, generics, lambdas and async/await all did, and when you look at code that was created prior to those features it definitely looks 'legacy' today.

SideburnsOfDoom 8y ago
> - and it will be hard not too look at the older methods as legacy. You're right, it will be legacy. And the job is to support the business, and that means maintaining, fixing, extending the existing code. The legacy code. It's going to be a long time until the bulk of it is up to date with all of this.