Mike J Innes
Mike J Innes
Actually, that's already implemented ;) Documentation is already attached to specific methods and it's easy in principle to grab the docstring for a specific method. It's not implemented for the...
> If the first element in a docstring's `.content` is a `Markdown.Code` then use that as the signature, otherwise automatically generate and display one based on the documented object. This...
Yeah, I think it's better to not have the opcode field (consider that it doesn't vary per `Return` object etc). You'll also have to handle things in a function for...
The short answer is "it isn't". We have a very basic interpreter that acts as a sanity check for some of our code generation, but it isn't complete and doesn't...
Actually `rest` can return either: ``` julia julia> Lazy.rest(constantly(1)) |> typeof Lazy.LazyList ``` Both `LinkedList` and `LazyList` are part of the same data structure, the `List`, and should behave in...
I think you're right that the issue here is that rest isn't lazily evaluated, although it doesn't always need to be lazy either. We can just overload it to be...
You can just `Pkg.checkout("MacroTools")` for now.
```julia using Poirot, IRTools coin() = rand(Bool) f = () -> begin a = coin() b = coin() observe(a | b) a & b end ``` Get a trace /...
Yup, good catch! Happy to take a PR to fix this, if you're up for it.
I'm not seeing this myself. Have you imported any other packages before Lazy.jl? > By the way, what is the @nobrace like macro? Can you clarify? Happy to help out...