and here’s a direct link to the
We’ve had a ton of discussion of this over the years, so I’m following the process and creating a PR with a completed design document.
It’s intended as a draft and comments are more than welcome. I’m trying to follow the process outlined in the readme on design-docs. This is me following step one:
Write a design document roughly following the template. Designs that do not present convincing motivation, demonstrate understanding of the impact of the design, or are disingenuous about the drawbacks or alternatives tend to be poorly received. Share it with the Stan core developers, advertising it on discourse and ideally the weekly meeting.
The next step is this:
Anyone involved may schedule meetings to discuss the design with interested parties over a video chat. It’s generally a good idea to get an approving stakeholder involved for at least one of these. A design may be postponed if we don’t want to evaluate the proposal immediately for reasons such as not being urgent or depending on other designs to be completed.
I’m happy to schedule meetings to discuss the proposal.
I’m particularly keen to get feedback from @Matthijs on this, particularly on whether we should impose covariance and contravariance on function and container types.