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

flatten empty tuple - fix #29112 #29548

Merged
merged 2 commits into from
Oct 8, 2018
Merged

flatten empty tuple - fix #29112 #29548

merged 2 commits into from
Oct 8, 2018

Conversation

KlausC
Copy link
Contributor

@KlausC KlausC commented Oct 6, 2018

As PR #29112 caused a performance regression, this is an attempt to solve the original issue without referring to the element type of Tuple{}.
The changes of 29112 are reverted, except the added test case.

@KristofferC
Copy link
Member

Could we add a test based on

julia> Base.return_types(Base.IteratorEltype, Tuple{Array})
1-element Array{Any,1}:
 Union{EltypeUnknown, HasEltype}

being fixed with this?

@JeffBezanson JeffBezanson merged commit 38612e0 into JuliaLang:master Oct 8, 2018
@KlausC KlausC deleted the krc/flatten-fix29112 branch October 8, 2018 19:53
KristofferC pushed a commit that referenced this pull request Oct 9, 2018
(cherry picked from commit 38612e0)
KristofferC pushed a commit that referenced this pull request Oct 10, 2018
(cherry picked from commit 38612e0)
KristofferC pushed a commit that referenced this pull request Feb 11, 2019
(cherry picked from commit 38612e0)
KristofferC pushed a commit that referenced this pull request Feb 20, 2020
(cherry picked from commit 38612e0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Must go faster
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants