Patching dependencies to work around compiler bugs

preview_player
Показать описание

00:00 Intro
03:45 Pull in audio playback library
18:45 Debugging compiler issue
58:40 Patching our dependency at build time
01:23:10 Playing a sin wave
Рекомендации по теме
Комментарии
Автор

ah yes i love when i find the exact question i'm looking for but it's an OPEN GH ISSUE on the COMPILER

angelcaru
Автор

11:00 i actually use b and p prefixes exclusively too. Its nice, when possible, to be able to work with variables without having to go look at type definitions.
The b prefix is just to shorten boolean names which otherwise i would prefix with "should" or "is" for example "shouldJump" becomes "bJump". Boolean variables names without some sort of prefix indicating it a boolean can be confusing as to what they actually are, in my opinion.
As for the p prefix i do that to avoid confusion about whether the variable is the actual thing or a pointer to the thing. It clearly indicates you should deref it if you want to access it.

I dont prefix any other variables with type info because i dont think it generally hinders you to work with them when you don't know whether its a U16 or a S32 or even a F64. If its a number, then its a number, as far as the logic you have in your head when you work with them.

DFsdfd
Автор

so crazy that that zig searches for dependency loops with DFS(basically a stack) but doesn't tell you either the stack or the duplicated value when it reports errors

blacklistnr
Автор

40:25 zig reduce needs to compile itself, then you can run -h on it.

CrossbowBeta
Автор

could we get a trimmed version of the qr seriers after this is finished? it was great but a little too long for me

salim
Автор

Most youtubers get around this by paying for editors =P

Jokes aside. Keep up the great work

Dje