{"push_id":1526665220,"size":7,"distinct_size":7,"ref":"refs/heads/master","head":"f939e452cc5884687f936bd25d51d4540d8f7c6f","before":"5d6e16eaaa7bba5ddac8fd9adabd4acc1aa2a161","commits":[{"sha":"908b156c8e1329d568eedc6dda5737eae01d1fb0","author":{"name":"FascinatedBox","email":"dd5c1965ff691801012f5b8241b947352d773db1@gmail.com"},"message":"api: Make the option struct internal.\n\nNow, options are created private to the interpreter. Get/set of\noptions is done through the state, instead of an option structure.\nThis eliminates problems with ownership regarding the options\nstructure. Now, option configuration takes place after\n`lily_new_state` and before the first parse/render call.","distinct":true,"url":"https://api.github.com/repos/FascinatedBox/lily/commits/908b156c8e1329d568eedc6dda5737eae01d1fb0"},{"sha":"c2727be22e21b8150a3a0eff4c4b6d32522b31c1","author":{"name":"FascinatedBox","email":"dd5c1965ff691801012f5b8241b947352d773db1@gmail.com"},"message":"dyna_tools: Wrap the dyna index in oct.\n\nThe indexes can otherwise subtly break in strange circumstances.","distinct":true,"url":"https://api.github.com/repos/FascinatedBox/lily/commits/c2727be22e21b8150a3a0eff4c4b6d32522b31c1"},{"sha":"7d1a9b8844212a48572bbf92ac520b8803675e0f","author":{"name":"FascinatedBox","email":"dd5c1965ff691801012f5b8241b947352d773db1@gmail.com"},"message":"syntax: Enums are now scoped if they use the `scoped` keyword.\n\nPreviously, an enum was scoped if it contained `.` before each\nvariant. More recently, I've decided I don't like that because:\n\n* It's really annoying to change between one kind of enum and another.\n  For enums with a handful of members, it's not a problem. But add\n  quite a few, and it's annoying.\n\n* It looks weird compared to what other languages do.\n\n* Using a keyword makes the distinction more easy to discover through\n  grep (you can grep for enum, then look for scope existing or not).\n\n* There's precedent for using a keyword in this way in the language\n  (protected and private are both qualifiers).\n\nI've also fixed dyna_tools.py so that `scoped enum` is now possible.","distinct":true,"url":"https://api.github.com/repos/FascinatedBox/lily/commits/7d1a9b8844212a48572bbf92ac520b8803675e0f"},{"sha":"74bf5d3b8962a404cb4b9d04fb8c76272c48a6c0","author":{"name":"FascinatedBox","email":"dd5c1965ff691801012f5b8241b947352d773db1@gmail.com"},"message":"syntax: Dynamic has pointer equality now.\n\nA long time ago, when Dynamic was called Any (and further back, when\nit was Object), it was a more transparent container. Values assigned\nto Any would implicitly get wrapped into Any, so this \"made sense\".\n\nI used to call that feature \"defaulting to Any\". I didn't like it.\nDynamic is more explicit, and I want to make it a necessary evil. So\ngive it sucky pointer equality, because this is the #1 way to have\ncomparison throw RuntimeError. Mind you, it's still possible for that\nto happen, but you need some very, very deep containers.","distinct":true,"url":"https://api.github.com/repos/FascinatedBox/lily/commits/74bf5d3b8962a404cb4b9d04fb8c76272c48a6c0"},{"sha":"429ec8a03934aacb22b1976f74a0f389955ede05","author":{"name":"FascinatedBox","email":"dd5c1965ff691801012f5b8241b947352d773db1@gmail.com"},"message":"syntax: Make Dynamic print like an instance too.\n\nThis makes Dynamic focus on being an opaque container for moving some\nvalue from A to B. Use it only if you need to.","distinct":true,"url":"https://api.github.com/repos/FascinatedBox/lily/commits/429ec8a03934aacb22b1976f74a0f389955ede05"},{"sha":"149b2cc63bad40d36953b0e008b2dcc328226235","author":{"name":"FascinatedBox","email":"dd5c1965ff691801012f5b8241b947352d773db1@gmail.com"},"message":"api: Either -> Result, lily_file_for_*, value api shuffling.\n\nMany people have rightfully (heh) mentioned in the past that Either\nought to be called Result instead. That Left and Right are more\nbaggage and not names that really convey a purpose. I was waiting\nfor a good time to do this, and I think this is it. So Either, Left,\nand Right are now Result, Failure, and Success (respectively).\n\nMore central to api, lily_file_ensure_* functions are gone in place\nof lily_file_for_*, which produce the raw file on success.\n\nThe last two changes are:\n\n* lily_push_super -> lily_instance_super, and put by\n  lily_new_instance to encourage proper use.\n\n* lily_is_valid_utf8 moved to be by the string handling functions.","distinct":true,"url":"https://api.github.com/repos/FascinatedBox/lily/commits/149b2cc63bad40d36953b0e008b2dcc328226235"},{"sha":"f939e452cc5884687f936bd25d51d4540d8f7c6f","author":{"name":"FascinatedBox","email":"dd5c1965ff691801012f5b8241b947352d773db1@gmail.com"},"message":"syntax: Rearrange operator precedences.\n\n* Function pipe is now below equalities.\n\n* Equalities are now entirely grouped together.\n\n* Bitwise operations are now grouped too.","distinct":true,"url":"https://api.github.com/repos/FascinatedBox/lily/commits/f939e452cc5884687f936bd25d51d4540d8f7c6f"}]}
{"actor":{"display_login":"FascinatedBox"}}