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.

Sign up for GitHub

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

@nospecialize for Returns #44853

Merged
merged 1 commit into from
Apr 5, 2022
Merged

@nospecialize for Returns #44853

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion base/operators.jl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -940,7 +940,7 @@ struct Returns{V} <: Function
Returns(value) = new{Core.Typeof(value)}(value)
end

(obj::Returns)(args...; kw...) = obj.value
(obj::Returns)(@nospecialize(args...); @nospecialize(kw...)) = obj.value
Copy link
Member

Choose a reason for hiding this comment

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

Would it make sense to allow f(_...; _...) in function definitions, i.e. repeat _ for both args and kwargs, and then insert automatically @nospecialize for _ arguments (if it's not already the case).

function show(io::IO, obj::Returns)
show(io, typeof(obj))
print(io, "(")
Expand Down