Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Julia complexity checks included a
switch
statement (which does not currently exist in Julia) but omittedelseif
andtry/catch/finally
(unlike Python).Also, the Julia checks oddly included two comparison operators
==
and!=
, which are not control flow (unlike the short-circuiting&&
and||
), are only two of the many comparison operators in Julia, and don't seem to be used as complexity measures by scc for Python. So I deleted these two from the list. Is there a good argument for why these should be included? (I see that a number of languages, like Ruby and C++, do include them for some reason.)I also considered adding Julia's
->
anddo
operators which create anonymous functions, but you don't use the analogouslambda
in Python so I left it out.