New package: MistyClosures v1.0.0

[JuliaRegistrator]

• Registering package: MistyClosures
• Repository: https://github.com/compintell/MistyClosures.jl
• Created by: @willtebbutt
• Version: v1.0.0
• Commit: ee522725df94c46c987c7e3e9a0ccf8f9c8fa6a6
• Reviewed by: @willtebbutt
• Reference: compintell/MistyClosures.jl@ee52272#commitcomment-142591375

[github-actions]

Your new package pull request met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

Since you are registering a new package, please make sure that you have read the package naming guidelines: https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[wsmoses]

Does this potentially make sense to move into Julia proper rather than a package? [noblock]

[willtebbutt]

[noblock] I would have no problem with this going in to Julia proper at some point, but I'd rather just make it a package for now in the interest of time.

[willtebbutt]

[noblock] @wsmoses would you mind [noblock]ing your comment so that this can be merged?

[wsmoses]

Sorry, am on travel presently. [noblock].

That said if moving into Julia proper is the goal, I feel like it might be productive to make an RFC / PR to Julia?

I know a lot of compiler things that might benefit from this so it's worth getting the design right from the get go.

[willtebbutt]

[noblock] I take your point -- I'll open an RFC / PR to Julia proper to get the ball rolling once this package is registered.

p.s. sorry, it still looks like your first comment is blocking merging 😬