David Hewitt
David Hewitt
> Both screenshot examples are identically underlined though? With my proposed patch, Zed matches VSCode, yes. Zed without my patch has the additional blue underline on the inactive code, which...
That's great, thank you.
Yes good point, I'll work on dropping the `once_cell` requirement 👍
Superseded by #4676
So changing the exact message `Create and return a new object. See help(type) for accurate signature.` is probably not possible. These all come from the type "slot wrappers" which take...
Yes, the same is true of these. I think the Python "slots" don't allow for documentation to be added, we would need to ask the CPython team for this.
That said, there is [`METH_COEXIST`](https://docs.python.org/3/c-api/structures.html#c.METH_COEXIST) which would allow us to install our own Python-level `__lt__` (which could then have documentation). This would be a change to the proc-macros but might...
The `state` is contained in an `UnsafeCell`, and we don't try to synchronize writes and reads because we require `py: Python` to e.g. `PyErr::value`
Not exactly, it consumes it's original state and rebuilds it in place when normalizing. You're right it's write once, though. I think the in place rebuild implies a lock if...
I realize that one option is to leave the design as is and just replace the `UnsafeCell` with a mutex on the freethreaded build. But I think that might have...