15:37 <oz> Did the Gitter bridge die ?

17:05 <oz> ugh... is there anything we can do to fix that?

23:16 <postmodern> if you rename a constant in your library, do you leave behind the old constant to alias the value?

23:17 <postmodern> i know crystal is kind of against aliases

23:18 <FromGitter> <tenebrousedge> I probably wouldn't bother

23:22 <postmodern> i mean, i am technically breaking semver, even though i only just released the library

23:24 <FromGitter> <kinxer> Then increase the minor version so it's clear that there could be breaking changes. If people are using your library with `shards`, they should probably be using a specific version or `~>`, in which case they will have to manually update to the new version (which is good).

23:26 <FromGitter> <tenebrousedge> the nice thing about Crystal, as opposed to Ruby, is that things like that will only ever be compile-time issues

23:35 <postmodern> semver dictates that break changes can only occur in major version bumps, though

23:35 <FromGitter> <Blacksmoke16> but if its pre `1.0.0` the minor is used to indicate breaking

23:36 <postmodern> hmm aliasing the constant gives me a weird error about `Error: undefined macro method 'Path#name'`. Probably a sign not to.

23:36 <FromGitter> <Blacksmoke16> add a `.resolve`

23:36 <FromGitter> <Blacksmoke16> `Type.resolve.name`

23:38 <FromGitter> <Blacksmoke16> but what are you trying to do?