00:30 <FromGitter> ... homogenous Array of symbol/string/char/... and inside the function will be doing a `map(&.to_s)`, but seems like a lot of possible combinations that need to be specified. ⏎ ⏎ Is there an easier or more compact way to represent this? [https://gitter.im/crystal-lang/crystal?at=611860324b7707158f81e7be]

00:30 <FromGitter> <nanobowers> Crystal's type system continues to be full of surprises (to me anyway). I would've thought that trying to pass in a value of `Array(Symbol)` into a function parameter that takes `Array(Symbol|String)` would be acceptable, but it appears I have to have that function parameter take `Array(Symbol) | Array(String) | Array(Symbol|String)` ⏎ ⏎ Ultimately i'd like to accept either a heterogenous or

01:48 <FromGitter> <Blacksmoke16> @nanobowers https://crystal-lang.org/reference/syntax_and_semantics/inheritance.html#covariance-and-contravariance

01:49 <FromGitter> <Blacksmoke16> also, whats your use case for using `Symbol`?

01:52 <FromGitter> <nanobowers> @Blacksmoke16 Thanks. Possible use of symbols mostly for user convenience and accepting something as close to ruby cut/paste as possible mainly for unittests

01:53 <FromGitter> <Blacksmoke16> Mmk, because they offer no benefit over a string, and an enum might also be better

09:01 <FromGitter> <HertzDevil> an `Array(T | U)` restriction can take both `Array(T)` and `Array(U)` arguments (although it really shouldn't), unless e.g. that parameter declares an instance variable

11:41 <FromGitter> <asterite> I would avoid mixing symbols and strings. In fact, I would avoid symbols entirely

15:45 <yxhuvud> frown. It would have been nice if shards would have cloned recursively. Oh well, I guess I'll have to reimplement that in the makefile.

15:46 <yxhuvud> before anyone asks, no the submodule is not crystal and not controlled by me.

16:39 <FromGitter> <nanobowers> thanks @asterite and @Blacksmoke16 for the guidance on symbols, sounds like the best bet is to avoid them almost entirely. ⏎ ⏎ A test related question: My program has a top level main() which prints things to either stdout or stderr and calls exit() with a value. I would like to be test main() and be able to trap the exit() with the error code and also grab stdout/stderr (presumably to an IO::Memory

16:39 <FromGitter> ... buffer). I am able to trap the exit via `Signal::*.trap`, but not sure how to get the process exit status. Also, since STDOUT/STDERR are constants, i can't temporarily modify them or figure out how to . `Process.new` covers most of this, but only seems suitable for executing shell programs, not crystal code. Is the only so ... [https://gitter.im/crystal-lang/crystal?at=6119432b949a3d73863a11db]

16:43 <FromGitter> <Blacksmoke16> i think you have a few options

16:43 <FromGitter> <Blacksmoke16> 1) Built your binary and just invoke it via `Process.run`

16:44 <FromGitter> <Blacksmoke16> 2) Abstract the logic within `#main` to not be so tightly coupled with STDOUT/STDERR. I.e. allow providing `IO` instance for those, defaulted to what you want. Then instead of `exit` just have it return a value.

16:45 <FromGitter> <Blacksmoke16> could also then have a dedicated CLI entrypoint that handles doing the `exit` if needed

23:20 <FromGitter> <postmodern:matrix.org> @nanobowers: I still need to port command_kit.rb to Crystal. It's API allows initializing the command class with a custom stdin, stdout, stderr, which can be StringIO instances that captures I/O and exit status'es are returned as an integer.

23:32 <FromGitter> <postmodern:matrix.org> ☝️ Edit (https://gitter.im/crystal-lang/crystal?at=6119a13a933ee46b755c1082): @nanobowers: I still need to port command_kit.rb to Crystal. It's API allows initializing the command class with a custom stdin, stdout, stderr, which can be StringIO instances that captures I/O and exit status'es are returned as an integer. ⏎ https://github.com/postmodern/command_kit.rb/blob/main/spec/stdio_spec.rb