ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
i509vcb has quit [Quit: Connection closed for inactivity]
pac85 has joined #zink
<pac85> zmike: so regarding what we where talking about yesterday. Say I have a zink_program generated before uber shaders are enabled, when they are enabled should uber shaders be compiled for that program or should that program keep on relying on synchronous variant compiles?
<zmike> I think ideally it shouldn't compile anything extra
<zmike> then again it could be the case that it later needs a legacy variant
<pac85> yeah
<zmike> 🤕
<zmike> I don't like this question
<pac85> hahaha
<pac85> they both feel like bad choiches
<pac85> though the second is easier to implement
<pac85> I already have logic to fall back to synchrously compiled variants so I just need to or something somewhere
Dark-Show has quit [Quit: Leaving]
hikiko has joined #zink
hikiko has quit [Read error: Connection reset by peer]
hikiko has joined #zink
hikiko has quit []
qyliss has quit [Remote host closed the connection]
pac85 has quit [Remote host closed the connection]
Plagman has quit [Remote host closed the connection]
qyliss has joined #zink
Plagman has joined #zink
bnieuwenhuizen has quit [Remote host closed the connection]
bnieuwenhuizen has joined #zink
i509vcb has joined #zink
jhli has quit []
jhli has joined #zink
jhli has quit []
jhli has joined #zink