Emilio Cobos Álvarez
Emilio Cobos Álvarez
Another trivial workaround would be to just add a `typedef PyObject MyPackage_PyObject;` to the generated bindings right?
I think it can be implemented using something like: ```rust unsafe fn push_unchecked(v: &mut ThinVec, value: T) { debug_assert!(v.capacity() > v.len()); let end = v.as_mut_ptr().add(v.len()); std::ptr::write(end, value); v.set_len(v.len() + 1);...
We'd need to test the constant code about basic casts.
There's another assumption that is that all OSes have a reasonable way of displaying an overlay scrollbar. This is now more and more the case, but browsers have to make...
To clarify... Chromium-based browsers don't seem to honor the system setting on Windows (Firefox does), and that seems like something that could be addressed and would improve the expected rendering...
(And without introducing inconsistent scrollbar styles for users)
Yeah part of the trick here is that for some cases where we need property-specific behavior we have a separate type. But it's a Rust type, not a CSS type....