{"push_id":2379572590,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b5e1a7e1576cade0a541081ebb141449150a9fae","before":"1972c9fb395eefbb4b8c79aaf801dbd6ba58fac4","commits":[{"sha":"b5e1a7e1576cade0a541081ebb141449150a9fae","author":{"name":"Brian Dickens","email":"a65c6e78dc3f50f9f27981507e78fe0d6e0c9073@gmail.com"},"message":"Kill DON'T experiment, turn into DO_FLAG_NO_PATH_GROUPS\n\nThe somewhat-cutely named \"DON'T\" operation was a variant of DO which\ncould skip across code and locate the end point of a DO/NEXT operation,\nbut without side-effects.  While it was a given that it could not\n*always* do this, some operations were thought to be scannable.  But it\nreally could only be used in such narrow circumstaces (e.g. a string of\nliterals and GET-WORD!s) that it wasn't useful.\n\nThis removes the operation and much of its supporting code, except for\nwhat was used to prevent the evaluation of a GROUP! in a path during\nsomething like a GET or a SET.  This prevents:\n\n    >> path: 'obj/(print \"side effect!\" 'key)\n\n    >> get path ;-- not obvious this would have side-effects\n    side effect!\n    == ...\n\nInstead users are asked to use EVAL or REDUCE to accomplish GET or\nSET when the PATH! will have side effects, and this raises an error.","distinct":true,"url":"https://api.github.com/repos/metaeducation/ren-c/commits/b5e1a7e1576cade0a541081ebb141449150a9fae"}]}
{"actor":{"display_login":"hostilefork"}}