Changes between Version 1 and Version 2 of WishList

11/25/12 14:31:19 (8 years ago)



  • WishList

    v1 v2  
    33This is the wish list. Don't be shy. Jot down your wishes here, or if it's something that really needs to fixed or done, [ fill out a ticket]. You can also start by mentioning these things on the discussion forum or IRC. 
     5== Proper Timeout mechanism == 
     7as part of simplifying the complicated things: a timeout keyword.  
     8the semantics and what it should actually do are debatable, but there should be an option for each scenario. 
     9for example, closing down a bad request, or maybe just resuming the code flow, maybe forcefully releasing resources, etc. 
     11I saw timeout integrated in the TCL language. (they had the os be the external "superviser" managing the time) 
     12I think erlang also has it, I don't remember maybe it was called 'after'. 
     13ofcourse erlang is a very different language, and its design and constructs reflect that. 
     15with the advent of c#5 it is now easier for the developer: async, await .. it's harder to get this wrong. 
     17ideally, the language can help the developer not even get to deadlock situations, race conditions etc. 
     18no shared state was erlang's solution, there are coroutines, mailboxes and message-passing in other languages. 
     19making the right constructs go a long way in this regard. 
     20in Eiffel, they now have scoop, which as i understand is something like a locked access to a resource, without manually wrapping the value in a class to do the locking. it solves a different part by (sort of) declaring dependencies. 
     22I think it is too complicated for a novice programmer to get right in C#. maybe cobra can provide an alternative way, where the tricky parts will be done by a library or compiler. 
    524== Eliminate argument repetition in lambdas ==