Marek Kaluba

on `CxxWrap-v0.10.1`: ```julia julia> @code_warntype Polymake.Integer(3) Variables #self#::Core.Compiler.Const(Polymake.Integer, false) arg1::Int64 Body::Polymake.IntegerAllocated 1 ─ %1 = Polymake.IntegerAllocated::Core.Compiler.Const(Polymake.IntegerAllocated, false) │ %2 = Core.apply_type(Polymake.Ptr, Polymake.Cvoid)::Core.Compiler.Const(Ptr{Nothing}, false) │ %3 = Base.getindex(Polymake.__cxxwrap_pointers, 41)::Tuple{Ptr{Nothing},Ptr{Nothing},Bool} │ %4...

pretty good find!

I've seen this error from time to time (when e.g. changing julia version?), and the standard (?) solution is to wipe `~/.julia/polymake_user`... I have no idea what is the root...

@rbehrends ?

```julia using Polymake function BB_iterator(c) N = polytope.dim(c) @info "running bb using iterator over $N-dimensional polytope" bb = Polymake.BeneathBeyond(c.POINTS, c.LINEALITY_SPACE, redundant=true, triangulation=true, iscone=true) tr = GC.@preserve bb begin for x...

I'd keep this one open as a reminder; To be honest in the long run the best option would be to create a separate `Polydb.jl` package that depends on `Polymake.jl`,...

@benlorenz thanks for looking into this! I'd just document this bug/feature as a design decision. Even in julia access to subfield must be `GC.@preserve`d when the validity of the subfield...

that's a nice picture;) I guess this could be closed?

ok, so that means that polymake always grabs the interrupt and does nothing with it? I thought what we set-up was passing the interrupt from julia to polymake **if we're...

I just meant that the only possibility of stopping the endless computation is to suspend and then kill julia process; What would be ideal is to pass the interrupt to...