continuous issue : new ideas

[arakov]

• compile type operator overriding
• expression patters
• DI
• analog of C# record
• switch expression
• prefix nullable / nable - allow to assign nil
• strong typed forward constant
• internal / protected conversion : should it be supported (see system'Symbol conversion from pointer)?
• interface mockup
• async constructor
• native actor/virtual actor model, like on elixir, to enable building fault tolerant and high scalable systems

[bencz]

• async constructor
• ( just thinking ) native actor/virtual actor model, like on elixir, to enable building fault tolerant and hight scalable systems

[arakov]

Sure. I've updated, It is a list of possible ideas, so any idea is welcome

[bencz]

Well, the actor/virtual actor, is something that i think is realllllly awesome!!

Check this out: https://www.erlang-solutions.com/blog/heres-why-you-should-build-scalable-and-concurrent-applications-with-elixir/

At now, I'm using a lot at my current job, but, im using this framework, since here where are work, we use mainly c#

https://github.com/asynkron/protoactor-dotnet

Just to give a sample to you, i have developed a polling system, where each cell phone makes a request to this system every 5s + ack request if there is some message to the cellphone...
Before i migrate the system to protoactor, we are using redis, but, we start to get a bunch of errors with network and connection lost with redis... and, a high cpu usage in each POD, because we need to use distributed locks and so on, now, using virtual actors, we have a really stable system, using much less cpu and each request we got a time reduction of 30ms in each request!!

Per hour, this system handle about of 2 milion requests

But, to have an actor model, async/await, sockets, switchs, tasks and some other stuffs from this issue, is necessary

[bencz]

Attributes for classes, methods and properties

[arakov]

They are already supported: see testCase / info for classes / functions, dto_prop / info for properties.

[bencz]

Oh, ok!
I probably missed this update/implementation... after github migrated the dashboard, it became more difficult to see/track the commits :(