stan::io::reader and stan::io::writer use

[Michael Betancourt]

Do stan::io::reader and stan::io::writer get used anywhere besides
when the parser generates model::transform_inits? I’m planning
on cleaning these up in refactoring the var_contexts and don’t
want to have any unintended side effects.

[Bob Carpenter]

The reader is used in

write_csv()
write_array()
log_prob()

Basically, everywhere you need to do the conversion from
unconstrained to constrained.

The writer is used in:

transform_inits()
write_csv_header()
write_csv()

In general, you can just look at a compiled model to see
where things get used. It's easier than tracing through the
code generator.

- Bob

> --
> You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>

[Michael Betancourt]

Follow up — nothing uses write_csv and write_csv_header, right?
This might be an excuse to deprecate them and maybe even clean
up write_array...

[Bob Carpenter]

I don't know about CmdStan, RStan, or PyStan. But
if none of those are using them, we can just get rid of
them. We don't even need to deprecate them.

- Bob

[Michael Betancourt]

CmdStan doesn’t, and I know all the places in the C++ side
of Stan that use those functions so that just leaves RStan
and PyStan. Do you guys use them at all?

[Allen B. Riddell]

PyStan doesn't. RStan has a test:

rstan/tests/cpp/blocker.hpp

-a

[Daniel Lee]

I wrote that test: it can be removed safely.

[Bob Carpenter]

The code generator's modular. All you need to do is remove
the function to write the CSVs. These are definitions of
generate_write_csv() and generate_write_csv_header(), along with
the calls to them in the generate_cpp() function.

- Bob