<FromGitter>
<Blacksmoke16> changing it to a class must cause LLVM to do something diff that is more performant :shrug:
Flipez has quit [Read error: Connection reset by peer]
Flipez has joined #crystal-lang
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #crystal-lang
Flipez has quit [Changing host]
Flipez has joined #crystal-lang
yxhuvud has quit [Read error: Connection reset by peer]
yxhuvud has joined #crystal-lang
alexherbo2 has quit [Ping timeout: 260 seconds]
alexherbo2 has joined #crystal-lang
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #crystal-lang
<FromGitter>
<djberg96> How do I get at some of the underlying stat info from `File.info`? Specifically I want to get at the blksize.
<FromGitter>
<Blacksmoke16> isnt the block size a file system thing and not a specific file?
<FromGitter>
<djberg96> I can see the `@st_blksize` inside what looks like a `LibC::Stat`
<FromGitter>
<djberg96> but am not sure how to get at it
<FromGitter>
<Blacksmoke16> oh
<FromGitter>
<Blacksmoke16> in that case looks like its not exposed in the public api of `File::Info` so would have to monkey patch in a getter for it i guess
<FromGitter>
<Blacksmoke16> ameba is more likely to be implemented sooner as well. if the compiler ends up getting user warnings like this eventually great, but better to have something at least
<FromGitter>
<moe:busyloop.net> true
<FromGitter>
<moe:busyloop.net> i'll try to remember to write a ticket later (gotta push my fix first 😬)
<FromGitter>
<Blacksmoke16> was also talk of setting up ameba CI on crystal repo, so would help that too
jhass[m] has quit [Quit: Bridge terminating on SIGTERM]
jhass[m] has joined #crystal-lang
walez has joined #crystal-lang
<FromGitter>
<azurelmao> > change it to an array of Int32 and `@blocks.insert i, 1` ⏎ ⏎ Can I make the capacity of the array constant? So as not to accidentally increase the size somehow
<FromGitter>
<azurelmao> @Blacksmoke16
<FromGitter>
<Blacksmoke16> you can give it an initial size, but that doesnt prevent it from getting bigger
<FromGitter>
<azurelmao> yhm I see
<riza>
if you plan ahead, you can!
<FromGitter>
<azurelmao> @Blacksmoke16 hey, remember how I asked you some time ago how to have a class var of the instance of that class?
<FromGitter>
<azurelmao> it was something like {new}
<FromGitter>
<azurelmao> what was it exactly?
<FromGitter>
<Blacksmoke16> `class_getter instance : self { new }`?
<FromGitter>
<azurelmao> ah yes that
<FromGitter>
<azurelmao> thank you
taupiqueur has quit [Quit: WeeChat 3.7.1]
walez has quit [Quit: Leaving]
alexherbo2 has joined #crystal-lang
<FromGitter>
<azurelmao> It seems to work, yet not at the same time :/ ⏎ https://carc.in/#/r/e5vz
taupiqueur has joined #crystal-lang
<FromGitter>
<Blacksmoke16> you're never `+= 1` the instance one. only the one you explicitly new up via `Foo.new`
<FromGitter>
<Blacksmoke16> `Foo.instance` would return the same instance. if you want to prevent someone from doing `Foo.new` would have to also define a private initializer
alexherbo2 has quit [Remote host closed the connection]
taupiqueur has quit [Quit: WeeChat 3.7.1]
renich has joined #crystal-lang
_ht has joined #crystal-lang
alexherbo2 has joined #crystal-lang
alexherbo2 has quit [Ping timeout: 260 seconds]
ur5us has joined #crystal-lang
<FromGitter>
<azurelmao> Ohh
<FromGitter>
<azurelmao> I thought what the {new} thing did was set it to an instance whenver .new was called
<FromGitter>
<Blacksmoke16> no, its the same as like `class_getter instance : self = new` but lazy. i.e. doesnt actually initialize the instance until you call `.instnace`