kit

Hi @sidwellr re: size-deferred vector: I've added [a comment on the open PR about it](https://github.com/processing/p5.js/pull/8203#issuecomment-3461547172) justifying this approach as follows. > First, it is in the spirit of p5.js to...

Hi everyone, thanks so much for all the lively discussion of the p5.js 2.x Vector implementation! Now that that 2.1 is released, we wanted to set up a more direct...

Hi everyone, thanks so much for all the lively discussion of the p5.js 2.x Vector implementation! Now that that 2.1 is released, we wanted to set up a more direct...

Hi @Satish-Medar, I've noticed a few requests for contributions on different topics - and I've also seen you've been working on some PRs already. Thank you for your enthusiasm! However,...

Hi everyone, thanks so much for all the lively discussion of the p5.js 2.x Vector implementation! Now that that 2.1 is released, we wanted to set up a more direct...

Thanks for this @davepagurek ! A few thoughts: > If the hook returns a new value as output, you can assign to the .result property of the hook After fiddling...

Thanks @davepagurek ! Based on the discord chat, here is another potential idea which assumes that we wouldn't want to support interleaving or nesting of the hooks, and that there's...

Hi everyone, thanks so much for all the lively discussion of the p5.js 2.x Vector implementation! Now that that 2.1 is released, we wanted to set up a more direct...

Hi @pratham-radadiya ! This issue is pretty wide and probably is best done in multiple partial and independent PRs, can you describe the specific scope of a PR you'd work...

Hi @pratham-radadiya sure, comment here when you're ready, and @lukeplowden can then also update what the status is / assign! Until then, if anyone else volunteers, they'd be welcome to...