06:44 <FromGitter> ... [https://gitter.im/crystal-lang/crystal?at=61b59a5c8f98cb0811bb46f7]

06:44 <FromGitter> <spTorin> If you need to transfer a result or an error code from the method (analog to Result in Rust). Which path is correct and more in line with the spirit in the crystal? ⏎ ⏎ 1) return tuple `{result<T>, Err}` and first check `if answer[1]` ⏎ 2) return Union `(result<T> | Err)` and first check `result.is_a?(Err)` ⏎ 3) simply call the method and handle all exceptions at the level above

06:51 <FromGitter> <oprypin:matrix.org> @spTorin: never 1, rarely 2, usually 3 if the error is the rare case

14:12 <FromGitter> <mehmethankut_twitter> is there a way to get all properties defined for an object? or should I write my own macro

16:24 <FromGitter> <naqvis> Crystal doesn't have reflections and no RTTI. So you will have to go with macro. Take a look at TypeNode (https://crystal-lang.org/api/1.2.2/Crystal/Macros/TypeNode.html) for all available `type` information you can retrieve at compile time.

16:45 <ngp> is it possible to chain Procs? Ie. a Proc function takes a &block argument and I want to chain an arbitrary list of them together

16:46 <ngp> where the input to each "higher level" proc is some args, and the next Proc in the chain

17:21 <FromGitter> <naqvis> you can try some kind of builder pattern here. something like https://carc.in/#/r/cfll

18:20 <ngp> I don't think that gives me exactly what I'm looking for. What I'm trying to implement is similar to a pipe-filter pattern, but using Procs

18:31 <FromGitter> <jrei:matrix.org> You'll have more luck by using OOP

18:34 <FromGitter> <jrei:matrix.org> For example, like done in `Array` with `select` and other methods, by mutating the same object then returning it

18:48 <ngp> so currently I have an array of Procs, but I think I can work with it by wrapping each proc, it's input, and the next proc in the chain in an object

18:59 <FromGitter> <Blacksmoke16> could also use an array of structs that have a `#call` method

19:14 <FromGitter> <jrei:matrix.org> That's like how `HTTP::Server` does.