{"push_id":1136645182,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"4a14b42cbcdf99b04be7080358d241fd48a43d30","before":"61811d6ff66bda6d7d41fa42446ec08d0a868204","commits":[{"sha":"4a14b42cbcdf99b04be7080358d241fd48a43d30","author":{"name":"Hostile Fork","email":"1d28577c3a34c1ac08d512237ad32156e7267b61@hostilefork.com"},"message":"Enhance legacy return-none-instead-of-void feature\n\nThis changes the rule for whether or not a none (BLANK!) is returned\nfrom operations like SELECT and IF to be sensitive not just to the\nlegacy mode switch, but to the flag encoded on the array of running\ncode regarding where it came from.\n\nHence, turning on the legacy return mode will not affect the authoring\nof mezzanine routines with different expectations.  The sensitivity to\nwhether the source was loaded before or after the r3-legacy mode was\nturned on will determine the behavior.\n\nThough not a perfect solution, it is an alternative (for the moment)\nto rebinding the source to adapted constructs.  Long-term, rebinding is\nthe right way to handle the issue (though having a feature of this\nkind could come in handy for things that cannot be solved that way.)","distinct":true,"url":"https://api.github.com/repos/hostilefork/rebol/commits/4a14b42cbcdf99b04be7080358d241fd48a43d30"}]}
{"actor":{"display_login":"hostilefork"}}