Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using in a package #50

Closed
gragusa opened this issue Dec 7, 2017 · 2 comments
Closed

Using in a package #50

gragusa opened this issue Dec 7, 2017 · 2 comments

Comments

@gragusa
Copy link

gragusa commented Dec 7, 2017

@mauro3 I would like to use SimpleTraits.jl in a package to build a generic interface. The idea is that other packages would add their types to the trait that I define in my package. I have two questions in this regard:

  1. Will the master be released soon? I saw there is a divergence between master and the last release and my understanding is that the released version does not work on 0.7.

  2. Assuming 1. is not a problem, is my plan sound? Would it make sense to do this or third-party packages will run into problems in adding their types to a trait defined in my package? (I guess not, but before venturing into a big refactoring I want to be sure.)

@mauro3
Copy link
Owner

mauro3 commented Dec 7, 2017

Cool, thanks for considering SimpleTraits!

  1. Will the master be released soon? I saw there is a divergence between master and the last release and my understanding is that the released version does not work on 0.7.

I can tag a release for Julia 0.7 if you want but 0.7 is moving target. So I'd rather you'd follow master for now, that keeps the burden lower for the good folks merging all the METADATA.jl PRs. Once 0.7 gets a feature freeze, then I'm planning to tag a version.

Note thought, that there is the still pending transition to where-function syntax, which will happen sometime soonish (but next year), see #46. Until then you have to live with deprecation warnings. Also, if you plan to write hundreds of @traitfn then this transition might be a hassle.

Assuming 1. is not a problem, is my plan sound? Would it make sense to do this or third-party packages will run into problems in adding their types to a trait defined in my package? (I guess not, but before venturing into a big refactoring I want to be sure.)

Yes, I think the grand plan is sound. This is what SimpleTraits aims to facilitate.

@mauro3
Copy link
Owner

mauro3 commented Aug 2, 2018

I think things are fixed here. In particular with #46 done. Re-open if you feel this is not the case.

@mauro3 mauro3 closed this as completed Aug 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants