Andrea Pagnani
Andrea Pagnani
... note also that given `xmat = [x[i][j] for i=1:length(x), j=1:3]` the `@save "xmat.jld" xmat` returns me a scary ``` -rw-r--r-- 1 pagnani staff 11976712 Oct 15 17:21 xmat.jld ```...
... and I forgot to say that I am on a ``` Julia Version 0.4.1-pre+1 Commit 70b42a6* (2015-10-08 06:21 UTC) Platform Info: System: Darwin (x86_64-apple-darwin14.5.0) CPU: Intel(R) Core(TM) i7-4870HQ CPU...
Hi Tim, I feel really sorry to come up to bother you at intermittent time with different problems. But, as usual, the solution you provided, i.e. turning on the `INLINE_TUPLE`...
Indeed it does not pass the tests. For the time being I'm ok with the flag solution. Thanks a lot as usual. It might however be useful to leave this...
Is JLD2 going to supersede JLD? Or the improvements are going to to be ported to JLD. I was under the impression that JLD would be a sort of standard...
Good to know! Completely off-topic: matlab has its own standard format to store data (.mat), other languages as well. Wouldn't be a good idea to move JLD into julia base...
I probably have the same problem ``` type T2 h::Vector{Tuple{Int,Int}} end x = T2([(1,2),(2,3)]) @save "x.jld" x @load "x.jld" ERROR: MethodError: `jlconvert!` has no method matching jlconvert!(::Ptr{Tuple{Int64,Int64}}, ::Type{Tuple{Int64,Int64}}, ::JLD.JldFile, ::Ptr{UInt8})...
Well the first lines of jld_types.jl are ``` # Controls whether tuples and non-pointerfree immutables, which Julia # stores as references, are stored inline in compound types when # possible....
Forgot to add versioninfo ``` julia> versioninfo() Julia Version 1.10.0 Commit 3120989f39b (2023-12-25 18:01 UTC) Build Info: Official https://julialang.org/ release Platform Info: OS: macOS (x86_64-apple-darwin22.4.0) CPU: 12 × Intel(R) Core(TM)...
Pinging @wsmoses which is the expert here ...