precompiled modules can't contain BigInts

[Keno]

__precompile__()
module Crash
const x = big"123"
__init__() = @show x
end # module

julia> using Crash
INFO: Precompiling module Crash...

signal (11): Segmentation fault
while loading no file, in expression starting on line 0
__gmpz_get_str at /home/ubuntu/julia-debugger/usr/bin/../lib/libgmp.so (unknown line)
base at ./gmp.jl:518
[inline] at ./gmp.jl:509
showall at ./show.jl:1428

[vtjnash]

Technically, this is a user error (for specifying __precompile__ incorrectly)

[Keno]

The user may have a pitch fork and know where you live.

[JeffBezanson]

Another reason to have fully native bigints that only call GMP for tricky functions.

[ChrisRackauckas]

@vtjnash could you explain how a user could avoid this issue?

[yuyichao]

Don't declare the the package as precompilable.

[ChrisRackauckas]

Is there less heavy-handed way? If it's only a small part of the package which is causing it, that seems like overkill.

[Ismael-VC]

Technically, this is a user error (for specifying precompile incorrectly)

@vtjnash technically this is a documentation error, I couldn't find a glimpse of bigs being discussed at the Module initialization and precompilation topic. ...issues and PRs are not documentation.

I'm sure bigs must have some kind of characteristic that makes it obvious (at least for you and a few others) that they wont work in this scenario, it would be better if you guys let others also know and why.

[yuyichao]

Anything with pointers.

[yuyichao]

And this is actually documented in the module doc in the section about precompilation

initializing global constants that involve pointers returned by external libraries

Documentation improvements are obviously welcome if that was not obvious/easy to find enough.

[ChrisRackauckas]

It's not just global constants though. In the other case I showed the constants were inside of a function inside of a module. (Unless constants in a function, when they are inline, somehow go global as an optimization I don't know about)

[ChrisRackauckas]

initializing global constants that involve pointers returned by external libraries

It should mention "this includes" and a few examples from Base that it includes. What other Base types have this problem?

[TotalVerb]

Given that @big_str is often emitted by the parser, it seems extremely brittle that having a large number in the AST somewhere can break precompilation. (this was #20749) This problem with large numbers is not covered by the existing initializing global constants that involve pointers returned by external libraries as, as far as I understand, function ASTs are not global constants, and should be documented separately.

module TestModule

function foo()
    170141183460469231731687303715884105728
    return 42
end

end

[Jutho]

I also struggled with this over at WignerSymbols.jl, but managed to make it work by storing the constant big number in a Ref container and initializing it with an __init__ function. But some assistance in the documentation would have helped.

[vtjnash]

fix (for BigFloat) in #27331