clover caruso
clover caruso
There isn't an issue to track this but I also want to make `$` accept raw strings instead of 'cooked' strings. I think @zackradisic already has this implemented. It reveals...
adding #2472 as well because i have basically all the code written for this i think there was just a failing test
this is likely the underlying cause of #7718
is `.git/config` synced to the remote. if not, then writing to it will cause a very confusing situation where one developers git environment is different from another without obvious reason...
ah, is it checking for an item named [name] and then finding the directory, then giving up? actually no, we dont run the module resolver for script names reminds me...
idk if this is a goodfirstissue but if someone wants to investigate the code, run command starts in run_command.zig line 1032 "pub fn exec("
note: to get more useful information of a core dump, download `bun-profile` from the github releases, and you can then debug a core from bun (non profile) with `lldb ./bun-profile...
wait this reads like the prettier crash fixed by increasing the stack size #7476. can you try the *latest* canary build?
@dylan-conway Stack overflow in a different function. Not a recursion bug but because the file given is literally 70kb and the recursion (probably comma operators) is *that* deep. ``` bun...
> smaller repro: wow, i get illegal instruction on this one.