Dirkjan Ochtman
Dirkjan Ochtman
> Sure! If someone sets `rustls_provider_ring`, not only every other provider should be turned off, any relevant defaults should be applied at this crate's level so that the preference doesn't...
Honestly not sure I'm motivated to review this code on a voluntary basis. Maybe your organization can sponsor this work?
> Through which channels would sponsoring happen? Directly in Github? That's probably easiest -- can also provide you with a contract if that works better for you.
https://github.com/rust-lang/rust/issues/132162 is coming, but will presumably take a while to be within our MSRV.
Hmm, I don't think there is a clean way to do this, but feel free to propose a design.
How would Askama detect whether the calling code is compiled in debug mode? As I understand it, each crate may be compiled with a separate profile, and as a procedural...
Yeah, I don't think any of this really makes sense. I suggest you write a custom procedural macro to abstract over the `bunch of ugly #[cfg_attr` on your templates.
My impression is that it's not being worked on -- I don't see any related open PRs. @HarrisonHemstreet are you still intending to work on it?
Nope, it hasn't been a priority for us. If someone wants to help out, that would be great!
Maybe we could install panic handler at the top level and print some suggestions when we catch a panic resulting from OOM? Not sure how easy to distinguish those would...