bbb23exposed
bbb23exposed
> Could you please provide the complete stack trace? You stripped the important part at the end. ``` Compiler crash traceback from this point on: File "Cython/Compiler/Visitor.py", line 182, in...
> If we followed the same pattern (which we probably should) Why? The way it works in python as is I describe above.
It would be nice if we could have the long and long long versions too, but unfortunately that results in "ambiguous overloaded method" on any call of float, even when...
> > It would be nice if we could have the long and long long versions too, but unfortunately that results in "ambiguous overloaded method" on any call of float,...
> I'd expect most usages to actually work on Python objects, so rather than implementing Python versions of `round()` that only call the builtin Python `round()` function, I think you...
~~Okay, I've implemented @scoder's suggestion. Unfortunately, it had to be accomplished by a hack implementing `_handle_simple_function_round` in `EarlyReplaceBuiltinCalls` instead of `OptimizeBuiltinCalls` and then calling `analyse_types` early on the argument to...
Okay, I made it work without the analyse_types() hack.
> > otherwise things [like] `1.0 + round(x)` would use Python conversions because type analysis would have already been done assuming the output was a PyObject. > > We still...
> I integrated a feature into 3.1 that will make this implementation easier. See [99e9df1](https://github.com/cython/cython/commit/99e9df17d2cabf5714eec9e844144720aea81a9d) You can now generate a dedicated function corresponding to the call arguments when encountering a...
> Interesting. I'd like to get some details about the exact situation: At some point in execution of the target, one of its calls to `malloc` necessitate the `valloc`ation of...