Da Li (李达)
Da Li (李达)
BTW, can I be upgraded to a collaborator? or can I be given the permission about marking issues and PRs? I can only use this permission to mark the issues...
Oh, if possible, I think this fix should be put in release ASAP, perhaps 0.60? For my use-cases (heavily using various numba containers and structref), my performance could be hurt...
> Would suggest to join a dev meeting or office hour and ask about this. Sure, will try. For the test case: I think if the jitted code is related...
reopen..., but I don't have the permission.
I think this can be added into next release rc?
HA, don't worry.
I wonder why my PR didn't break the related tests for jitclass type annotation support. The test cases: ```python def test_type_annotations(self): spec = [("x", int32)] @jitclass(spec) class Test1(object): x: int...
seconded. Python provides a way (`-0` or `-O0`) to disable assert: https://docs.python.org/3/using/cmdline.html#cmdoption-O.
not sure why this failed. ``` Found required file: docs/upcoming_changes/9478.improvement.rst Checking naming convention. Passed: Filename is valid Checking file contents: support assign a ``tuple`` to a row of a ``recarray``...
oh, the reason is ``` Traceback (most recent call last): File "/Users/dali/Code/open-numba/maint/towncrier_rst_validator.py", line 98, in assert len(title) == len(underline), "Title and underline must be the same length." + \ AssertionError:...