Conversation

Notices

1. Embed this notice
   Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 15-Apr-2026 12:14:08 JST Rich Felker

   • anna
   • pinskia

   @pinskia @navi I feel like this is more of an ideological want than a practical one. Are there ever bugs from lack of a mechanism to force the type match here? The call point choosing the callback and context object type to pass has both of those as static things not some complex runtime variable.

   • Embed this notice
     pinskia (pinskia@hachyderm.io)'s status on Wednesday, 15-Apr-2026 12:20:45 JST pinskia

     in reply to

     • anna

     @dalias @navi

     Yes I have one case where I was moving from one callback to another and I forgot to change the context object.

     I only noticed when I reviewed the code. It was able to compile; stopping at compile would have saved me time.

     In this case; the original call back was checking a hashset to see if an edge was in that set and we added all edges into that hashset except for the latch.
     the new callback only checked one edge. So I was trying to speed up the code :).