| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
instruction/expr text
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
history info
|
|
|
|
|
|
|
|
This is technically correct (and for illustration):
```py
>>> "asdf"""
'asdf'
>>> "asdf""qwer"
'asdfqwer'
>>> def foo():
... "asdf"""
... return 4
...
>>> foo()
4
>>> foo.__doc__
'asdf'
```
But as it currently exists, it messes up some (admittedly, incorrect)
lexers/syntax highlighters (e.g. emacs's python-mode).
|
|
|
|
|
|
|
|
|
|
|
|
ContextMenuManager is now a subclass of QObject and that can break operator= (only seen on windows builds)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
eliminate stale xrefs.
|
|
fix state initialization.
|
|
|
|
|
|
installation
|
|
|
|
|
|
|
|
|
|
|
|
Change include_directories to `&[AsRef<Path>]`
Make TypeParserResult default and clone
Change error_msg scope
cargo fmt
Kyle's comments
Whackamole with .as_ptr() as _
Fixed up error_msg as BnString
|
|
|
|
|
|
|
|
TSAN sees a data race in AddRef()
|
|
|
|
|
|
|
|
|
