Catherine
Catherine
Yes, effectively turning Python classes into Rust traits, which are a much better runtime model. That would also give us a sane way to implement polymorphism.
I don't think that should go into 3.5. It's not a bug but an artefact of how imported names are represented (they're basically just locals), and it's not trivial to...
It's the same as (2). The compiler can see that the two functions are one and same, and types inferenced for the local name propagate to the non-local name.
> And the take home message is that the compiler is unable to infer stuff about attributes of modules? Only that global type inference interacts badly with the polymorphic integer...
That's RPC throughput in the list.
It certainly won't be quick as I don't have an easy way to reproduce the issue. But it will be possible.
Remote TTL is faster than local TTL?
You can think of the ARTIQ Python compiler to override all built-in types. The ARTIQ Python language is a subset of Python proper for several good reasons. First, the experiments...
> Is this due to the fact that experiments must not have a runtime dispatch, and tuples are capable of holding values of different types? Absolutely correct. You can deconstruct...
Inhomogeneous lists in kernels are impossible to implement. What is possible is implementing iteration through tuples using `for` loops: ``` for x in self.beamlines: x.set_ttl_off() ``` This would be expanded...