Jacob Wujciak-Jens

Hey @mjskay! As discussed {touchstone} is now in a stable state, would love your feedback!

I have skimmed the blog post and it looks interesting, I'm guessing that they wanted to use this in an ML context? My only issue with this is that it...

>I agree - but that cat is already out of the bag :joy_cat: That is true,not sure how to improve that situation. I think an extra package is too much...

This looks very useful but it would not work as expressions (#75 ) as this is not valid r syntax. I am sure there is a way we can do...

@kgoldfeld would changing the order of the definition table columns cause problems in you workflow or do you think for other reasons it is a bad idea? I would like...

Hm. Why not go all out then and do `param1 param2 param3` to make it distribution agnostic? The problem with what you write in your second paragraph is backwards compatibility,...

I see where you are coming from... and again it shows that this is true: >There are only two hard things in Computer Science: cache invalidation and **naming things**. --...

As a reference here my current poc https://gist.github.com/assignUser/af104a19c2b6819043bd7e290117e5cd Generation is not finished yet but defining stuff works for now. At the moment I feel that it is a bit clunky...

I though so and didn't want to get rid of the idea of documenting the data generation process, just using another form factor. But I am not sure what that...

I published a first sketch of how this could work with using S3 methods here: https://github.com/kgoldfeld/simstudy/blob/issue-75-no-more-strings/R/no_strings.R I currently think that it is pretty cumbersome internally and it might restrict us...