marijnfs_ has quit [Read error: Connection reset by peer]
<wilsonk>
hmm, the hover doesn't seem to work for @intCast, works for hovering over a local function and for id's and such though
<metaleap>
too bad
<fengb>
Ah you mean `fs.readAllAlloc`
<fengb>
I'm glad it's finding real problems. My biggest worry was being a site of false positives
<wilsonk>
metaleap: any way to tell it where my stdlib is?
<metaleap>
wilsonk: what editor are you using btw, if vscode do you rely on some generic "lsp client" extension?
<metaleap>
in the stderr logpanel for the lsp you'd see shortly after startup (or restart) after "init wiplangserver" and "enter main loop" a line like `STDLIB/home/_/a/zig/lib/zig/std` --- if detection succeeds, that is. otherwise silent nothingness as of today
<wilsonk>
metaleap: vscode with the andersfr extension
<metaleap>
wilsonk: no way to tell it anything right now, at the end things will be made configurable tho. it's the kind of thing i like to postpone until the full space of what could be in there is known.
<wilsonk>
metaleap: yep, no problems...just curious
<mikdusan>
oh nice. 21 seconds to build stage1 on llvm-10 branch. lld was costly.
slurpie has joined #zig
_whitelogger has joined #zig
* daurnimator
waves
<daurnimator>
andrewrk: would now be a better time?
<daurnimator>
andrewrk: is there a reason a lot of the lib/std/zig/cross_target.zig functions return a [:0]u8 rather than a []u8? I don't think the call sites want null-terminated and might be an artifact of accidental use of std.Buffer
ur5us has quit [Ping timeout: 256 seconds]
waleee-cl has quit [Quit: Connection closed for inactivity]
slowtyper has joined #zig
jrl has quit [Ping timeout: 240 seconds]
ur5us has joined #zig
ur5us has quit [Ping timeout: 256 seconds]
alva has joined #zig
metaleap has joined #zig
dddddd has quit [Ping timeout: 260 seconds]
jjido has joined #zig
alexnask_ has joined #zig
jjido has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
marijnfs has joined #zig
jjido has joined #zig
marijnfs_ has joined #zig
marijnfs has quit [Ping timeout: 265 seconds]
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 256 seconds]
mahmudov has quit [Ping timeout: 258 seconds]
marijnfs_ has joined #zig
marijnfs has quit [Ping timeout: 260 seconds]
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 255 seconds]
jjido has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
marijnfs_ has joined #zig
marijnfs has quit [Ping timeout: 256 seconds]
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 255 seconds]
marijnfs_ has joined #zig
marijnfs has quit [Ping timeout: 258 seconds]
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 258 seconds]
marijnfs_ has joined #zig
marijnfs has quit [Ping timeout: 265 seconds]
jjido has joined #zig
frett27 has joined #zig
return0e_ has joined #zig
return0e_ has quit [Remote host closed the connection]
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 260 seconds]
frmdstryr has joined #zig
slurpie has quit [Read error: Connection reset by peer]
marijnfs_ has joined #zig
marijnfs has quit [Ping timeout: 255 seconds]
dddddd has joined #zig
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 256 seconds]
knebulae has quit [Read error: Connection reset by peer]
<adamkowalski>
andrewrk: is there any way to "tag" unit tests and then when you run your suite only run tests with that tag? And can we generate some sort of report such as how long each test took to run, sorted from longest to shorted?
<TheLemonMan>
there's the test-filter option
<adamkowalski>
right but that seems to only filter tests in the first you are running
<adamkowalski>
I have a main file which includes all my other tests, similar to the standard library
<adamkowalski>
if you try to filter by a tag, it will run no tests, since main.zig has no tests of it's own
metaleap has joined #zig
wootehfoot has joined #zig
_Vi has joined #zig
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 260 seconds]
alexnask has joined #zig
<metaleap>
is there a "downloads" archive with the n most-recent nightly binaries? current one bugs out on me with "TODO buf_write_value_bytes maybe type" but dont want to downgrade to my weeks-ago nightly
<metaleap>
(this is the issue wilsonk warned me about yesterday so at least i wanna find out how-many-days-ago this regression began to show up in zig)
<metaleap>
jaredmm thx will try! funky that this whole machinery goes to town on every commit
<metaleap>
but sure handy
<metaleap>
(oh i see i guess commit msgs flag or unflag the process as only some have green checkmarks, ok good old ci/cd)
frett27 has quit [Ping timeout: 265 seconds]
slurpie has joined #zig
decentpenguin has joined #zig
wootehfoot has quit [Ping timeout: 265 seconds]
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 265 seconds]
<metaleap>
man some time in the last 10 days someone removed `error{OutOfSpace}` from some of the out-stream io stuff. was it in sliceOutStream? io/OutStream? beats me, all i know is that i relied on it for json-dumping and dynamically growing my buf until it would fit the json dump. now there's just a generic "WriteError".
alichay has quit [Ping timeout: 240 seconds]
<jaredmm>
@metaleap: there was a commit (c81345c8aec56a108f6f98001666a1552d65ce85) that changed OutOfSpace errors to OutOfMemory errors (with a lot of other file changes).
<jaredmm>
Maybe that can help you diagnose what changed and if there's a different way to handle it now.
adamkowalski has quit [Quit: Lost terminal]
marijnfs_ has joined #zig
<metaleap>
jaredmm nice find, thanks! i did a search in issues and in PRs on OutOfSpace with nothing turning up, how do you grep in situations like this?
marijnfs has quit [Ping timeout: 258 seconds]
<jaredmm>
If you have a working and unworking commit, you can use git bisect to narrow it down. You said 10 days, so I picked a random commit on that day and today.
<metaleap>
jaredmm til thx!
<jaredmm>
Git will ask you if a commit is good or bad and you have to run whatever test case you're doing to determine that, then it'll keep going until it finds the one that changed it.
<jaredmm>
You could also use git log to search for a specific string (like WriteError). `git log -S'WriteError' --after="2020-02-26" -p ./lib/std` and that should do a raw string search for anything that added that text (think it only works for adds and not removes).
<jaredmm>
Looks like -G'error.OutOfSpace' would work for removed ones (and uses regex rather than just a string).
decentpenguin has quit [Quit: decentpenguin]
<metaleap>
ooh that'd be the ticket, noted
<metaleap>
wilsonk through an hour or two of trial and error i drilled down the latest zig commit that still builds the wip lsp , i made an issue #4674 to track that zig regression
<metaleap>
andrewrk: so if i read https://github.com/ziglang/zig/commit/c81345c8aec56a108f6f98001666a1552d65ce85 correctly then the prior "OutOfSpace" errors must really be handled as if they were bog-standard general OutOfMemory errors? guess one can no longer auto-translate in their mind any OutOfMemory occurrence into "alloc fail" when scanning over code bases
dddddd has quit [Remote host closed the connection]
Akuli has quit [Quit: Leaving]
slurpie has quit [Ping timeout: 240 seconds]
marijnfs has joined #zig
marijnfs_ has quit [Ping timeout: 265 seconds]
LakeByTheWoods has joined #zig
slurpie has joined #zig
<wilsonk>
metaleap sorry I was afk. Checked out the issue. I can't see anything off hand that would cause that issue, but hopefully someone else with more experience can eyeball it.
<metaleap>
fingers crossed
alexnask_ has joined #zig
alexnask has quit [Ping timeout: 258 seconds]
daurnimator has quit [Ping timeout: 272 seconds]
frmdstryr has quit [Read error: Connection reset by peer]
TheLemonMan has quit [Quit: "It's now safe to turn off your computer."]