01:22 <FromGitter> <Blacksmoke16> ::raise

01:22 <FromGitter> <Blacksmoke16> You're overriding it so it's not actually raising

06:38 <Elouin> Is there an example of a crystal project using (interpreted) crystal as an extension language?

12:12 <repo> Blacksmoke16: omg... :facepalm:

12:12 <repo> Is this a bug? File.match?("test/**/*_test.rb", "test/foo/bar/baz_test.rb") # => false

12:13 <repo> it matches "test/foo/bar_test.rb"

12:13 <repo> but somehow the double star isn't correctly handled

12:16 <repo> i looked at the implementation but it's pretty um, complicated :P

12:23 <repo> interesting.. this one matches: File.match?("test/**/test", "test/foo/bar/test")

12:24 <repo> so probably the **/* is the issue here

12:47 <FromGitter> <moe:busyloop.net> still looks like a crystal bug to me. when someone tries to override `raise` then ⏎ the compiler should halt and play a voice-sample of asterisk shouting "don't do that"

12:54 <FromGitter> <Blacksmoke16> naw, its valid

12:54 <FromGitter> <Blacksmoke16> could run into the same problem if you override any top level method

19:09 <FromGitter> <spuun> Anyone using Spectator? I have a strange issue where my spec works if I just run that file (`crystal spec spec/class_specs.cr`), but if I run all specs (`crystal spec`) i get `Error: @instance_vars are not yet allowed in metaclasses: use @@class_vars instead`. ⏎ If i remove `expect(mocked_obj).to_not have_received(:method).with(SomeClass)` i dont get the error anymore. I should probably try to make a small

19:09 <FromGitter> ... example that reproduces it. Hm.

21:33 <FromGitter> <Blacksmoke16> reducing it and creating an issue would be the way to go

21:33 <FromGitter> <Blacksmoke16> otherwise, just use the stdlib `Spec` module and not have to deal with it

21:50 <Na_Klar> is there a risc-v port planned for crystal in the meanwhile?

21:51 <FromGitter> <Blacksmoke16> there is https://github.com/crystal-lang/crystal/pull/11980, but not sure what the status of it is atm

21:57 <Na_Klar> Blacksmoke16: do I get that right, that these commits are in the compiler's compile source code, and would make it able to bootstrap the compile for riscv? theoretically?

21:57 <Na_Klar> (I tried that myself some time ago and failed at the llvm problem, which seems to be solved with that commit, maybe ..)

22:02 <Na_Klar> ah or is that "just" for cross-compile?

22:11 <FromGitter> <Blacksmoke16> im not sure

22:12 <FromGitter> <Blacksmoke16> i'd guess cross compiling

22:16 <Na_Klar> yeah makes sense. and would be sufficient for me.