Skip to content

Commit

Permalink
Bump patch version (#6)
Browse files Browse the repository at this point in the history
  • Loading branch information
willtebbutt authored Jul 4, 2024
1 parent 0ddb0d2 commit 5322b32
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "MistyClosures"
uuid = "dbe65cb8-6be2-42dd-bbc5-4196aaced4f4"
authors = ["Will Tebbutt", "Frames White", "Hong Ge"]
version = "1.0.0"
version = "1.0.1"

[compat]
julia = "1.10"
Expand Down
5 changes: 5 additions & 0 deletions src/MistyClosures.jl
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ MistyClosure(ir::IRCode; kwargs...) = MistyClosure(OpaqueClosure(ir; kwargs...)

(mc::MistyClosure)(x::Vararg{Any, N}) where {N} = mc.oc(x...)

# You can't deepcopy an `IRCode` because it contains a module.
function Base.deepcopy_internal(x::T, dict::IdDict) where {T<:MistyClosure}
return T(Base.deepcopy_internal(x.oc, dict), x.ir)
end

export MistyClosure

end
3 changes: 3 additions & 0 deletions test/runtests.jl
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,7 @@ using Core: OpaqueClosure
# Default constructor.
mc_default = MistyClosure(OpaqueClosure(ir; do_compile=true), ir)
@test @inferred(mc_default(5.0) == sin(5.0))

# deepcopy
@test deepcopy(mc) isa typeof(mc)
end

2 comments on commit 5322b32

@willtebbutt
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/110393

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v1.0.1 -m "<description of version>" 5322b324164baa368c8a9ae702f5097aff256353
git push origin v1.0.1

Please sign in to comment.