[dependabot]

Updates the requirements on JET to permit the latest version.
Updates JET to 0.13.0

Release notes

Sourced from JET's releases.

v0.13.0

JET v0.13.0

Diff since v0.12.3

CHANGELOG

Added

• Added support for Julia v1.14. JET now loads full functionality on Julia 1.14 instead of empty stubs.

• Added the allow_unsupported_julia preference, which loads full JET functionality on unsupported Julia versions, e.g. nightly builds, without the development features that JET_DEV_MODE also enables:

  LocalPreferences.toml

  [JET]
  allow_unsupported_julia = true # previously `JET_DEV_MODE = true` was needed

  JET emits a warning when it is loaded on an unsupported Julia version this way, since it may not work correctly there.

• JETInterface now exports has_problems, the predicate that call_test_ex and func_test use to decide whether an analysis result fails a test.

• Calls whose matching methods are ambiguous are now reported as AmbiguousMethodErrorReport instead of MethodErrorReport saying that no matching method is found. For a union-split call, the ambiguous signatures are reported separately from those without any matching method:

  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  m(x::Int) = k(x, x)               # reported: ambiguous `k(::Int, ::Int)`
  n(x::Union{Int,String}) = k(x, x) # reported: ambiguous `k(::Int, ::Int)`
                                    # and no method for `k(::String, ::String)`

• invoke calls that throw MethodError because no method matches the specified signature are now reported as MethodErrorReport in the :basic and :sound modes, and those whose matching methods are ambiguous are reported as AmbiguousMethodErrorReport:

  f(::Int) = 1
  g(x) = invoke(f, Tuple{String}, x) # reported: no method for `f(::String)`
  h(x) = @invoke f(x::Integer)       # reported: no method for `f(::Integer)`
  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  l(x) = @invoke k(x::Int, x::Int)   # reported: ambiguous `k(::Int, ::Int)`

... (truncated)

Changelog

Sourced from JET's changelog.

[0.13.0]

Added

• Added support for Julia v1.14. JET now loads full functionality on Julia 1.14 instead of empty stubs.

• Added the allow_unsupported_julia preference, which loads full JET functionality on unsupported Julia versions, e.g. nightly builds, without the development features that JET_DEV_MODE also enables:

  LocalPreferences.toml

  [JET]
  allow_unsupported_julia = true # previously `JET_DEV_MODE = true` was needed

  JET emits a warning when it is loaded on an unsupported Julia version this way, since it may not work correctly there.

• JETInterface now exports has_problems, the predicate that call_test_ex and func_test use to decide whether an analysis result fails a test.

• Calls whose matching methods are ambiguous are now reported as AmbiguousMethodErrorReport instead of MethodErrorReport saying that no matching method is found. For a union-split call, the ambiguous signatures are reported separately from those without any matching method:

  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  m(x::Int) = k(x, x)               # reported: ambiguous `k(::Int, ::Int)`
  n(x::Union{Int,String}) = k(x, x) # reported: ambiguous `k(::Int, ::Int)`
                                    # and no method for `k(::String, ::String)`

• invoke calls that throw MethodError because no method matches the specified signature are now reported as MethodErrorReport in the :basic and :sound modes, and those whose matching methods are ambiguous are reported as AmbiguousMethodErrorReport:

  f(::Int) = 1
  g(x) = invoke(f, Tuple{String}, x) # reported: no method for `f(::String)`
  h(x) = @invoke f(x::Integer)       # reported: no method for `f(::Integer)`
  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  l(x) = @invoke k(x::Int, x::Int)   # reported: ambiguous `k(::Int, ::Int)`

• Top-level analysis now reports a @test that always fails, i.e. whose expression is inferred to evaluate to false or to a non-boolean value, and a @test_throws that always fails, i.e. whose expression is inferred to throw only exceptions that do not match the expected one. The errors in the

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions