-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: JuliaLang/julia
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 018e46d
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: JuliaLang/julia
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: ac5d042
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 17 commits
- 78 files changed
- 14 contributors
Commits on Oct 15, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 485495f - Browse repository at this point
Copy the full SHA 485495fView commit details -
Configuration menu - View commit details
-
Copy full SHA for a11d804 - Browse repository at this point
Copy the full SHA a11d804View commit details
Commits on Oct 18, 2021
-
This PR allows the use of `else` inside try-blocks, which is only taken if no exception was caught inside `try`. It is still combinable with `finally` as well. If an error is thrown inside the `else` block, the current semantics are that the error does not get caught and is thrown like normal, but the `finally` block is still run afterwards. This seemed like the most sensible option to me. I am not very confident about the implementation of linearization for `trycatchelse` here, so I would appreciate it if @JeffBezanson could give this a thorough review, so that I don't miss any edge cases. I thought we had an issue for this already, but I couldn't find anything. `else` might also not be the best keyword here, so maybe we can come up with something clearer. But it of course has the advantage that it is already a Julia keyword, so we don't need to add a new one. Co-authored-by: Jeff Bezanson <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 0357b2a - Browse repository at this point
Copy the full SHA 0357b2aView commit details -
Configuration menu - View commit details
-
Copy full SHA for b45b9bb - Browse repository at this point
Copy the full SHA b45b9bbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 806b128 - Browse repository at this point
Copy the full SHA 806b128View commit details -
Configuration menu - View commit details
-
Copy full SHA for ecc0398 - Browse repository at this point
Copy the full SHA ecc0398View commit details -
sparse: Optimize swaprows!, swapcols! (#42678)
We have a swpacols! helper in Base that is used in the permuation code as well as in the bareiss factorization code. I was working on extending the latter, among others to sparse arrays and alternative pivot choices. To that end, this PR, adds swaprows! in analogy with swapcols! and adds optimized implementations for SparseMatrixCSC. Note that neither of these functions are currently exported (though since they are useful, we may want a generic swapslices! of some sort, but that's for a future PR). While we're at it, also replace the open-coded in-place circshift! by one on SubArray, such that they can automatically beneift if that method is optimized in the future (#42676).
Configuration menu - View commit details
-
Copy full SHA for 225c543 - Browse repository at this point
Copy the full SHA 225c543View commit details -
Merge pull request #42668 from JuliaLang/jn/42645
codegen: add missing jl_get_fieldtypes calls
Configuration menu - View commit details
-
Copy full SHA for 1b64755 - Browse repository at this point
Copy the full SHA 1b64755View commit details -
7
Configuration menu - View commit details
-
Copy full SHA for 50fcb03 - Browse repository at this point
Copy the full SHA 50fcb03View commit details
Commits on Oct 19, 2021
-
Configuration menu - View commit details
-
Copy full SHA for e1d831b - Browse repository at this point
Copy the full SHA e1d831bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 02f7861 - Browse repository at this point
Copy the full SHA 02f7861View commit details -
Configuration menu - View commit details
-
Copy full SHA for df81a0d - Browse repository at this point
Copy the full SHA df81a0dView commit details -
Remove MSVC / ICC specific code (#42703)
Support for building MSVC and ICC was removed from the build system in PR #42586; this patch removes more leftover code which was there to support MSVC / ICC.
Configuration menu - View commit details
-
Copy full SHA for dc74954 - Browse repository at this point
Copy the full SHA dc74954View commit details -
Document effect of type aliases on global level (#42666)
Adds the sentence @JeffBezanson proposed to the documentation and solves #30824.
Configuration menu - View commit details
-
Copy full SHA for b55bfec - Browse repository at this point
Copy the full SHA b55bfecView commit details
Commits on Oct 20, 2021
-
🤖 Bump the Pkg stdlib from 2a4a5534 to bb180de2 (#42701)
Co-authored-by: Dilum Aluthge <[email protected]>
2Configuration menu - View commit details
-
Copy full SHA for 792c026 - Browse repository at this point
Copy the full SHA 792c026View commit details -
inference: forward
Conditional
inter-procedurallyThe PR #38905 only "back-propagates" conditional constraint (from callee to caller), but currently we don't "forward" it (caller to callee), and so inter-procedural constraint propagation won't happen for e.g.: ```julia ifelselike(cnd, x, y) = cnd ? x : y @test Base.return_types((Any,Int,)) do x, y ifelselike(isa(x, Int), x, y) end |> only == Int ``` This commit complements #38905 and enables further inter-procedural conditional constraint propagation by forwarding `Conditional` to callees when it imposes a constraint on any other argument, during constant propagation.
Configuration menu - View commit details
-
Copy full SHA for 07fd6e7 - Browse repository at this point
Copy the full SHA 07fd6e7View commit details -
inference: improve constant-prop' heuristics
- remove `const_prop_rettype_heuristic` since it handles rare cases, where const-prop' doens't seem to be worthwhile, e.g. it won't be so useful to try to propagate `Const(Tuple{DataType,DataType})` for `Const(convert)(::Const(Tuple{DataType,DataType}), ::Tuple{DataType,DataType} -> Tuple{DataType,DataType}` - rename `is_allconst` to `is_all_overridden` - also minor refactors and improvements added
Configuration menu - View commit details
-
Copy full SHA for ac5d042 - Browse repository at this point
Copy the full SHA ac5d042View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 018e46d...ac5d042