You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -190,7 +190,7 @@ The Julia community uses [GitHub issues](https://github.com/JuliaLang/julia/issu
190
190
Issues and pull requests should have self explanatory titles such that they can be understood from the list of PRs and Issues.
191
191
i.e. `Add {feature}` and `Fix {bug}` are good, `Fix #12345. Corrects the bug.` is bad.
192
192
193
-
You can make pull requests for incomplete features to get code review. The convention is to open these a draft PRs and prefix
193
+
You can make pull requests for incomplete features to get code review. The convention is to open these as draft PRs and prefix
194
194
the pull request title with "WIP:" for Work In Progress, or "RFC:" for Request for Comments when work is completed and ready
195
195
for merging. This will prevent accidental merging of work that is in progress.
196
196
@@ -209,6 +209,7 @@ Add new code to Julia's base libraries as follows (this is the "basic" approach;
209
209
Build as usual, and do `make clean testall` to test your contribution. If your contribution includes changes to Makefiles or external dependencies, make sure you can build Julia from a clean tree using `git clean -fdx` or equivalent (be careful – this command will delete any files lying around that aren't checked into git).
210
210
211
211
#### Running specific tests
212
+
212
213
There are `make` targets for running specific tests:
213
214
214
215
make test-bitarray
@@ -346,8 +347,8 @@ please remove the `backport-X.Y` tag from the originating pull request for the c
346
347
347
348
### Git Recommendations For Pull Requests
348
349
349
-
- Avoid working from the `master` branch of your fork, creating a new branch will make it easier if Julia's `master` changes and you need to update your pull request.
350
-
- Try to [squash](https://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) together small commits that make repeated changes to the same section of code so your pull request is easier to review. A reasonable number of separate well-factored commits is fine, especially for larger changes.
350
+
- Avoid working from the `master` branch of your fork. Create a new branch as it will make it easier to update your pull request if Julia's `master` changes.
351
+
- Try to [squash](https://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) together small commits that make repeated changes to the same section of code, so your pull request is easier to review. A reasonable number of separate well-factored commits is fine, especially for larger changes.
351
352
- If any conflicts arise due to changes in Julia's `master`, prefer updating your pull request branch with `git rebase` versus `git merge` or `git pull`, since the latter will introduce merge commits that clutter the git history with noise that makes your changes more difficult to review.
352
353
- Descriptive commit messages are good.
353
354
- Using `git add -p` or `git add -i` can be useful to avoid accidentally committing unrelated changes.
if source_mode == SOURCE_MODE_ABI && ci isa CodeInstance &&!ci_has_invoke(ci)
1241
-
inspected =IdSet{CodeInstance}()
1242
-
tocompile =Vector{CodeInstance}()
1243
-
push!(tocompile, ci)
1244
-
while!isempty(tocompile)
1245
-
# ci_has_real_invoke(ci) && return ci # optimization: cease looping if ci happens to get compiled (not just jl_fptr_wait_for_compiled, but fully jl_is_compiled_codeinst)
ci isa CodeInstance &&!ci_has_invoke(ci) ||return ci
1245
+
codegen =codegen_cache(interp)
1246
+
codegen ===nothing&&return ci
1247
+
inspected =IdSet{CodeInstance}()
1248
+
tocompile =Vector{CodeInstance}()
1249
+
push!(tocompile, ci)
1250
+
while!isempty(tocompile)
1251
+
# ci_has_real_invoke(ci) && return ci # optimization: cease looping if ci happens to get compiled (not just jl_fptr_wait_for_compiled, but fully jl_is_compiled_codeinst)
0 commit comments