Owen Green

Yes, I'd done something silly: if I correct to ` matrix[4,4] Rho;` (not `[2,2]`) the error goes away. Hopefully that helps narrow it down.

Thanks! > Are you using the latest RStan? ```r > rstan::stan_version() [1] "2.32.2" ``` The current version is 2.34? I'll try upgrading, after checking the effect of optimization. > Do...

* With `O0` and `Oexperimental` I get `Exception: matrix assign columns:...` * With `O1` I get `capacity exceeded` Correction to version given above. Both `rstan` and `StanHeaders` are 2.32.5, which...

A more minimal and self-contained reproduction. tl;dr in `O1` only, I get the internal error. Other flags correctly hint at what I did wrong: ```r stanmodelcode

This looks grand. I'll give it an experimental merge and test when I can. A general sclang question: is there any naming convention for denoting classes as being for internal...

Looks like it was changed to the handrolled thing in c1f7725d71748d9c3807f0d8ed607adf78f4f31b because the native parsing was enforcing a change of types somewhere undesirable.

@g-roma do you happen to remember what `parseYAMLFie` was doing that was undesirable?

The problem seems to be that `parseYAML` and friends make *everything* a `String`, e.g. ```supercollider d = "{\"foo\":[1.0,2.0,3,4,5]}".parseJSON d["foo"].do{|x| x.class.postln} ``` ``` -> Dictionary[ (foo -> [ 1.0, 2.0, 3,...

see https://github.com/supercollider/supercollider/issues/1154 which has been open since 2014 looks like yaml-cpp doesn't provide a nice way to determine whether a scalar is a string, int or float (see https://stackoverflow.com/questions/19994312/obtain-type-of-value-stored-in-yamlnode-for-yaml-cpp)

Thanks for the heads up @dyfer. It may well cause ABI issues between the current release build and a build of scsynth using the newer Boost. If it causes widespread...