02:52 <FromGitter> <sahar.sedaghat_gitlab> hello; I am trying to build Scry on debain amd64 machine and I am getting this:

02:52 <FromGitter> <sahar.sedaghat_gitlab> ``````

02:53 <FromGitter> <sahar.sedaghat_gitlab> (https://files.gitter.im/5588134315522ed4b3e2629f/PqEW/image.png)

02:54 <FromGitter> <sahar.sedaghat_gitlab> any solution for this? I think it is a known issue. Yes?

03:18 <FromGitter> <Blacksmoke16> using `1.4.1`?

03:18 <FromGitter> <Blacksmoke16> fwiw might have better luck with https://github.com/elbywan/crystalline

03:18 <FromGitter> <Blacksmoke16> ref: https://github.com/crystal-lang-tools/scry/issues/186

03:55 <FromGitter> <sahar.sedaghat_gitlab> @Blacksmoke16 What is the main ideas behind crystal.

03:55 <FromGitter> <sahar.sedaghat_gitlab> desktop app development/web devel!?

03:56 <FromGitter> <sahar.sedaghat_gitlab> is it similar to C++ or more of Ruby/Python type

03:56 <FromGitter> <sahar.sedaghat_gitlab> i.e it is compiled or interpreted?

03:59 <FromGitter> <Blacksmoke16> ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=62bd1fb6904f20479a55fbe1]

04:03 <FromGitter> <Blacksmoke16> syntax is ruby like, but compiled and statically typed. Id say with a focus on web dev, just because that part has the larger ecosystem atm

10:29 <FromGitter> <naqvis> Published CrystalVips (https://github.com/naqvis/crystal-vips) shard for Crystal bindings to the *libvips image processing library*

10:32 <hightower2> looks pretty useful naqvis

10:33 <hightower2> See if you can get Crystal mentioned in the list of bindings on https://www.libvips.org/ :-)

10:39 <FromGitter> <naqvis> yeah, will raise an issue there to see what process they follow to get bindings added to their docs

15:13 <riza> @naqvis thats excellent! <3

15:42 <FromGitter> <naqvis> thanks

16:08 <yxhuvud> 2k lines of lib bindings. Did you write it all yourself or did you use some tool to generate it?

16:08 <riza> I wasn't going to ask

16:09 <riza> I looked at building bindings for libvips and quickly decided I didn't have the experience in automation to make that happen

22:53 <bastienleonard> hi, is there a way to require the caller to use the value returned by a function (at compile-time)? A compiler warning would be OK if an error is not possible.

22:53 <FromGitter> <Blacksmoke16> got an example?

22:54 <bastienleonard> my use case is for "monadic" error handling, like Result in Ocaml/Rust

22:55 <bastienleonard> I want the compiler to tell me if I'm discarding some returned values

22:55 <FromGitter> <Blacksmoke16> pretty sure thats not a thing

22:55 <bastienleonard> I mean, the return value of some methods

22:56 <FromGitter> <Blacksmoke16> ```some_method```

22:56 <FromGitter> <Blacksmoke16> by default there isnt a way to say like "you should not ignore the return values of 'some_method'"

22:57 <bastienleonard> thanks for confirming

22:57 <bastienleonard> I wonder if there is some macro hack for this. I haven't looked into Crystal macros yet

22:57 <FromGitter> <Blacksmoke16> not sure, never really had a need for this

23:00 <bastienleonard> alright thanks. Going to stick to exceptions for this use case for now. I do find it convenient to require the caller to handle errors sometimes.