17:54 <FromGitter> <ym418_twitter> @Blacksmoke16 Thank you. I will duplicate the enum.

18:58 <wwalker> yxhuvud: thanks

22:49 <SamantazFox> Hello there! I have a language question this time: is it possible to "map" exceptions from one module to another?

22:50 <SamantazFox> https://play.crystal-lang.org/#/r/dxoe

22:51 <SamantazFox> In this example, I'd like to have a `Test::BadPatternError` exception, rather than a `File::BadPatternError` one

22:53 <SamantazFox> My struggle is that the `DB::Pool` is used in multiple places in the code, but that causes the same exception name to be displayed after the error message

23:01 <SamantazFox> Ideally, I want to avoid this: https://play.crystal-lang.org/#/r/dxom

23:05 <SamantazFox> (The final problem is that we have pool issues being reported as DB issues, but it isn't actually a DB issue but a problem with a specific part of the code using the `DB::Pool` logic)