News for hackers. Stuff that matters.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by codeulike on Tuesday October 15, 2019 @04:11AM (#21256472)
- Allow functions outside of classes

What do you mean? Isn't that just anonymous functions?

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by oblio on Tuesday October 15, 2019 @04:17AM (#21256509)
He wants top level functions. He wants to not have to write classes if he thinks the domain doesn't need modelling as objects.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by arethuza on Tuesday October 15, 2019 @04:24AM (#21256532)
You can have static classes that can contain nothing but static members - so effectively a namespace with no instantiation of that class allowed so no objects.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by oblio on Tuesday October 15, 2019 @04:37AM (#21256607)
I know, but many people dislike boilerplate code.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by manigandham on Tuesday October 15, 2019 @04:24AM (#21256536)
You can use a static class though. It's 1 class that then just behaves like a namespace and doesn't need any object modeling.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by jmkni on Tuesday October 15, 2019 @05:48AM (#21256955)
You could create an F# class library, put your functions in there, and then call them from C#?
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by e12e on Tuesday October 15, 2019 @04:21PM (#21263282)
They probably wants to not have to write classes if he thinks the domain doesn't need modelling as classes.

Objects are just initialized memory with a vtable, or actors that sends and receives messages...