jhass changed the topic of #crystal-lang to: The Crystal programming language | https://crystal-lang.org | Crystal 0.35.1 | Fund Crystal's development: https://crystal-lang.org/sponsors | GH: https://github.com/crystal-lang/crystal | Docs: https://crystal-lang.org/docs | Gitter: https://gitter.im/crystal-lang/crystal
<FromGitter> <Blacksmoke16> nice was able to do some refactoring, brought compile time for specs down from 27s to 5s
<FromGitter> <Blacksmoke16> big unions are bad ok
<FromGitter> <Blacksmoke16> say i have a `Regex` constraint, and you want to validate a non string value what would you think is most ideal:
<FromGitter> <Blacksmoke16> 1) Cast the value to a string ⏎ 2) Throw an exception (because it has to be a string)
<FromGitter> <Blacksmoke16> 1) Noop
_whitelogger has joined #crystal-lang
<FromGitter> <Blacksmoke16> i think im leaning towards 1, prob would pair well with custom `to_s` methods and such
_whitelogger has joined #crystal-lang
kotrcka has joined #crystal-lang
deavmi has quit [Ping timeout: 240 seconds]
deavmi has joined #crystal-lang
f1refly has joined #crystal-lang
f1reflyylmao has quit [Ping timeout: 260 seconds]
_whitelogger has joined #crystal-lang
<FromGitter> <mattrberry> Anyone have any feedback/criticism for my bitfield macro? It's my first macro that's more than a couple lines. At the moment it accomplishes everything that I wanted it to, but I'd love to know if there's anything that I could be doing better! https://github.com/mattrberry/bitfield
<FromGitter> <mattrberry> One thing I'd like to add is the ability to override the setters on the inheriting classes, but I'm not sure that that's possible in my current implementation since I add the methods in the `finished` macro..
<FromGitter> <mattrberry> I also plan on adding a to_s method sometime soon :)
_whitelogger has joined #crystal-lang