These are chat archives for ensime/ensime-atom

15th
Jul 2016
Viktor Hedefalk
@hedefalk
Jul 15 2016 15:05
@mdedetrich Yeah, I actually went with nested case classes. Hlists didn't really make sense to my use case of mapping the fields of a legacy db into some other integration protocol. Too much risk of messing up with the ordering. An hlist of 40 strings or ints interspersed… If I map the named fields of the table definitions to named case classes then I have decent code completion all the way and can't really mess it up. I'm still struggling with ever having a real practical use case of hlists :)
Ghost
@ghost~540393fe163965c9bc2018ce
Jul 15 2016 15:53
Is mostly useful in library code
Compile time marshalling, etc