[swift-evolution] Swift null safety questions

Matthew Johnson matthew at anandabits.com
Mon Mar 13 19:54:01 CDT 2017

Sent from my iPad

On Mar 13, 2017, at 6:35 PM, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> wrote:

>> On Mar 12, 2017, at 12:20 PM, Austin Zheng via swift-evolution <swift-evolution at swift.org> wrote:
>> Otherwise, if you really need to build a web server framework that can swallow any sort of application logic without choking, perhaps Swift as it currently stands isn't the best tool for the job.
> Or you should use a prefork server. As long as the supervisor process—which should be pretty small and simple—doesn't crash, the worker processes can trip assertions all day and only the single request will be affected.
> Processes are good. Processes are nice. Learn to love processes.
> (I suspect that, if we ever do support recovering from assertions, the mechanism will be fairly process-like: Very little data sharing between the thread/section permitted to crash and the outside world, with post-crash cleanup being handled by simply releasing all the memory allocated by the thread/section.)

I suspect you're right about this for the most part but I think we will want the ability for "failable processes" (or whatever they're called) to have read-only access to shared state that outlives them.  What I can't imagine is allowing them write access to state that is shared.

> -- 
> Brent Royal-Gordon
> Architechies
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list