19:15 <FromGitter> <Blacksmoke16> got updates and deletes working in my PoC

19:16 <FromGitter> <Blacksmoke16> ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=5f25bf876334d26a7e6ac2db]

19:16 <FromGitter> <Blacksmoke16> notice unchanged values are not included in the update query

19:57 <FromGitter> <chasestory> @watzon yeah, I am in salt lake, sorry for the delay in response.. Crazy week at work!

20:47 <FromGitter> <j8r> @Blacksmoke16 looks clean so far! You may have an idea on this: I'm doing a byte protocol - order matters. In my out-of-the-box (de)serialization library, I need to have this information somehow. Having an annotation on top of the object sounds good, like `Crystalizer::Object(fields_order: ["first_ivar", "another_one", "etc"])`. I like better than having to write one with an index on each ivar.

20:49 <FromGitter> <j8r> Now, it would be great to have information about this order in the API docs – how would you do this?

20:49 <FromGitter> <j8r> Maybe generate comments with macros...

20:51 <FromGitter> <j8r> Ho, and for `String` and `Bytes` type, an annotation is needed to know the max size.

20:52 <FromGitter> <Blacksmoke16> annotations arent documented in the API docs atm so yea

20:53 <FromGitter> <Blacksmoke16> maybe you could add docs to the type, but not sure if that would totally override the other docs on it or what

20:53 <FromGitter> <j8r> I wonder, it is possible to generate comments for an object with an annotation?

20:54 <FromGitter> <Blacksmoke16> additionally maybe define some pseudo constant that you could apply the comment/order to

20:54 <FromGitter> <j8r> I see what you mean by overwriting the comments

20:55 <FromGitter> <j8r> Got an idea, the object annotation can have an option to tell that

20:55 <FromGitter> <Blacksmoke16> you can do something like

20:55 <FromGitter> <Blacksmoke16> ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=5f25d6d903d73b60ee5e20d6]

20:56 <FromGitter> <Blacksmoke16> (https://files.gitter.im/5588134315522ed4b3e2629f/KXit/image.png)

20:56 <FromGitter> <Blacksmoke16> but you lose the original docs yea

20:56 <FromGitter> <j8r> :thinking:

20:56 <FromGitter> <Blacksmoke16> > additionally maybe define some pseudo constant that you could apply the comment/order to

20:57 <FromGitter> <j8r> Yep

20:57 <FromGitter> <Blacksmoke16> thats be fairly easy to do

20:57 <FromGitter> <j8r> Which had a name that can be customized with the annotation!

20:57 <FromGitter> <Blacksmoke16> there you go :p

20:58 <FromGitter> <j8r> Thank you, that's a good idea :slight_smile:

20:58 <FromGitter> <Blacksmoke16> np, better solution would be showing the annotations + values on a type/method etc but thats another story...

20:59 <FromGitter> <j8r> I agree, for sure

21:39 <FromGitter> <yorci> does File.read_lines locks file?

21:40 <FromGitter> <yorci> multiple instance program got deadlock by shared file (i guess)

21:40 <FromGitter> <yorci> one of that instances is still working while others became zombie

22:01 <FromGitter> <Blacksmoke16> probably not?

22:02 <FromGitter> <lebogan> Any way to get 0.35.1 for raspberrypi? At 0.33.0 now from the public portilier.com. Thanks.

22:02 <FromGitter> <Blacksmoke16> cross compiling it yourself or maybe using docks would be easiest

22:04 <FromGitter> <lebogan> Thanks. I'll give cross compiling another try

22:29 <FromGitter> <Blacksmoke16> wew, got `find` support now

22:30 <FromGitter> <Blacksmoke16> `em.find User, 1 # => #<User:0x7fc5f30aacc0 @alive=true, @id=1, @name="Jim">`

22:34 <FromGitter> <Blacksmoke16> since the em manages the states of the entities, if you were to do it twice, it wouldn't need to make a query the second time since its already managed