Skip to content

Issues: JuliaLang/julia

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Should broadcast extrude to match length 0 dimensions breaking This change will break code broadcast Applying a function over a collection needs decision A decision on this change is needed
#32663 opened Jul 23, 2019 by mbauman
Remove \uparrow and \downarrow from infix operator list? breaking This change will break code parser Language parsing and surface syntax speculative Whether the change will be implemented is speculative unicode Related to unicode characters and encodings
#31639 opened Apr 6, 2019 by MasonProtter
deprecate <<, >>, >>> on BitArray arrays [a, r, r, a, y, s] breaking This change will break code deprecation This change introduces or involves a deprecation
#30958 opened Feb 4, 2019 by JeffBezanson Potential 2.0
pointer(A::Array{T}) has misleading type for non-bitstype A arrays [a, r, r, a, y, s] breaking This change will break code minor change Marginal behavior change acceptable for a minor release speculative Whether the change will be implemented is speculative
#30276 opened Dec 5, 2018 by chethega
remove exports get_zero_subnormals / set_zero_subnormals breaking This change will break code maths Mathematical functions
#30027 opened Nov 14, 2018 by musm Potential 2.0
begin in indexing expression (possibly inside macro call) breaking This change will break code needs decision A decision on this change is needed parser Language parsing and surface syntax
#29920 opened Nov 3, 2018 by alyst
stop exporting HTML and Text from Base breaking This change will break code
#29841 opened Oct 29, 2018 by musm Potential 2.0
deprecate randn((1,2)) breaking This change will break code deprecation This change introduces or involves a deprecation randomness Random number generation and the Random stdlib speculative Whether the change will be implemented is speculative
#29653 opened Oct 15, 2018 by cossio Potential 2.0
redesign typeof(::Type) breaking This change will break code types and dispatch Types, subtyping and method dispatch
#29368 opened Sep 25, 2018 by JeffBezanson Potential 2.0
repeated variables in tuple destructuring silently overwrite breaking This change will break code compiler:lowering Syntax lowering (compiler front end, 2nd stage) needs decision A decision on this change is needed
#29089 opened Sep 7, 2018 by tpapp
Implement AbstractVector{T}(r::AbstractRange), fix #27138 breaking This change will break code
#28956 opened Aug 29, 2018 by jw3126 Loading…
WIP/RFC: extend date formats with markers for optional and fixed length markers breaking This change will break code dates Dates, times, and the Dates stdlib module
#28741 opened Aug 18, 2018 by bug-brain Loading…
Ambiguous syntax with operator suffixes breaking This change will break code parser Language parsing and surface syntax
#28441 opened Aug 4, 2018 by perrutquist
Precedence of ± operator breaking This change will break code parser Language parsing and surface syntax
#28050 opened Jul 11, 2018 by ChrisRackauckas
Implement broadcasting for AbstractDict and NamedTuple breaking This change will break code broadcast Applying a function over a collection
#26158 opened Feb 22, 2018 by andyferris Loading…
What to do about multivalue setindex!? arrays [a, r, r, a, y, s] breaking This change will break code broadcast Applying a function over a collection
#24086 opened Oct 10, 2017 by mbauman
Move to a factory pattern for array creation arrays [a, r, r, a, y, s] breaking This change will break code design Design of APIs or of the language itself speculative Whether the change will be implemented is speculative
#22630 opened Jun 30, 2017 by davidanthoff
Reserve/add and and or with relaxed semantics from [left] only short-circuiting, e.g. allowing & or | breaking This change will break code speculative Whether the change will be implemented is speculative
#19933 opened Jan 8, 2017 by PallHaraldsson
what should we use { } for? breaking This change will break code needs decision A decision on this change is needed
#8470 opened Sep 25, 2014 by JeffBezanson Potential 2.0
Remove require, import, and maybe importall and merge into using breaking This change will break code design Design of APIs or of the language itself modules speculative Whether the change will be implemented is speculative
#8000 opened Aug 14, 2014 by quinnj
Make use of mapslices consistent throughout Julia breaking This change will break code needs decision A decision on this change is needed
#3893 opened Jul 31, 2013 by johnmyleswhite
ProTip! Mix and match filters to narrow down what you’re looking for.