Bump @nomicfoundation/slang from 1.2.0 to 1.2.1

[dependabot]

Bumps @nomicfoundation/slang from 1.2.0 to 1.2.1.

Release notes

Sourced from @​nomicfoundation/slang's releases.

v1.2.1

Patch Changes

• #1377 f3b51be Thanks @​ggiraldez! - Bind untyped tuple deconstruction elements as references, not declarations

• #1335 6c3ad5d Thanks @​ggiraldez! - Top-level ConstantDefinitions now bind to their type and resolve extension functions called on them

• #1338 18be0bc Thanks @​ggiraldez! - Make try/catch parameters and vars in for loop initialization available in Yul

• #1339 f16e4b5 Thanks @​ggiraldez! - Fixes to the binding rules in Solidity:

  • Make the .length member available in all static-size byte arrays
  • Allow assembly blocks (and nested Yul functions) to access inherited state variables
  • Allow assembly blocks access to constructor/modifier/fallback parameters
  • msg.sender is of address type (not payable) until 0.5.0
  • Top-level constants need to be visible from assembly blocks in files that import them
  • Resolve named arguments when calling an extension function
  • Imported symbols using deconstruction syntax can be bound in assembly blocks

• #1353 8e718dd Thanks @​ggiraldez! - Fixes to the binding rules in Solidity:

  • Values of the deprecated byte type have a length member until 0.8.0
  • Bind a qualified identifier in the same contract, ie. Foo.x in a method body of Foo
  • Correctly bind external constants and built-ins in nested functions in assembly blocks
  • Literal boolean values should bind to the bool type to chain extension functions
  • Public state variables the generate getters should have members of external functions (such as .selector)
  • Event types have a selector member

• #1326 045179b Thanks @​ggiraldez! - Fixes to binding rules:

  • Update TupleDeconstructionStatement so that their definiens is the TypedTupleMember/UntypedTupleMember for each variable declared.
  • Update YulVariableDeclarationStatement so that their definiens is the YulIdentifier for each variable declared.

• #1350 0594fe8 Thanks @​ggiraldez! - Fixes to bindings rules in Solidity:

  • Allow binding of using directives inside interfaces in Solidity < 0.7.1
  • Bind literal fixed arrays types
  • Fix generating binding graph for built-ins: remove the memory location specifier from types so they bind properly
  • Fix return type of value() and gas() legacy call options to allow chaining them
  • Bind legacy call options in the result of new expressions
  • Bind output type of public getters when the state variable is a nested mapping or array
  • A using directive with the global modifier should impact the source unit's lexical scope
  • Relax the Solidity version where the transfer() method works for non-payable addresses; this is a workaround for a Solidity quirk that makes it possible to do address(uint160(to)).transfer(amount) even after 0.5.0
  • Fix bound return types of wrap() and unwrap() methods of a user value defined type
  • Resolve the type of min() and max() of type() expressions for integer types to the integer type given in the expression operand
  • Fix binding of fully qualified modifier invocations
  • Fix #1321: min() and max() for type() expressions on enum types should bind only after Solidity 0.8.8
  • Bound type for literal number expressions is uint256 by default; this allows correctly binding extension methods operating on literal values
  • The type bytes is an array type and should bind the push() and pop() methods
  • Contract or interface reference values implicitly inherit from the address type on Solidity < 0.5.0

... (truncated)

Changelog

Sourced from @​nomicfoundation/slang's changelog.

1.2.1

Patch Changes

• #1377 f3b51be Thanks @​ggiraldez! - Bind untyped tuple deconstruction elements as references, not declarations

• #1335 6c3ad5d Thanks @​ggiraldez! - Top-level ConstantDefinitions now bind to their type and resolve extension functions called on them

• #1338 18be0bc Thanks @​ggiraldez! - Make try/catch parameters and vars in for loop initialization available in Yul

• #1339 f16e4b5 Thanks @​ggiraldez! - Fixes to the binding rules in Solidity:

  • Make the .length member available in all static-size byte arrays
  • Allow assembly blocks (and nested Yul functions) to access inherited state variables
  • Allow assembly blocks access to constructor/modifier/fallback parameters
  • msg.sender is of address type (not payable) until 0.5.0
  • Top-level constants need to be visible from assembly blocks in files that import them
  • Resolve named arguments when calling an extension function
  • Imported symbols using deconstruction syntax can be bound in assembly blocks

• #1353 8e718dd Thanks @​ggiraldez! - Fixes to the binding rules in Solidity:

  • Values of the deprecated byte type have a length member until 0.8.0
  • Bind a qualified identifier in the same contract, ie. Foo.x in a method body of Foo
  • Correctly bind external constants and built-ins in nested functions in assembly blocks
  • Literal boolean values should bind to the bool type to chain extension functions
  • Public state variables the generate getters should have members of external functions (such as .selector)
  • Event types have a selector member

• #1326 045179b Thanks @​ggiraldez! - Fixes to binding rules:

  • Update TupleDeconstructionStatement so that their definiens is the TypedTupleMember/UntypedTupleMember for each variable declared.
  • Update YulVariableDeclarationStatement so that their definiens is the YulIdentifier for each variable declared.

• #1350 0594fe8 Thanks @​ggiraldez! - Fixes to bindings rules in Solidity:

  • Allow binding of using directives inside interfaces in Solidity < 0.7.1
  • Bind literal fixed arrays types
  • Fix generating binding graph for built-ins: remove the memory location specifier from types so they bind properly
  • Fix return type of value() and gas() legacy call options to allow chaining them
  • Bind legacy call options in the result of new expressions
  • Bind output type of public getters when the state variable is a nested mapping or array
  • A using directive with the global modifier should impact the source unit's lexical scope
  • Relax the Solidity version where the transfer() method works for non-payable addresses; this is a workaround for a Solidity quirk that makes it possible to do address(uint160(to)).transfer(amount) even after 0.5.0
  • Fix bound return types of wrap() and unwrap() methods of a user value defined type
  • Resolve the type of min() and max() of type() expressions for integer types to the integer type given in the expression operand
  • Fix binding of fully qualified modifier invocations
  • Fix #1321: min() and max() for type() expressions on enum types should bind only after Solidity 0.8.8
  • Bound type for literal number expressions is uint256 by default; this allows correctly binding extension methods operating on literal values
  • The type bytes is an array type and should bind the push() and pop() methods

... (truncated)

Commits

• 53b08ab Bump Slang Version (#1332)
• a5faf5b Revert "Add NonterminalNode.create() and TerminalNode.create() to JS API ...
• f45b858 Revert path display lint (#1378)
• d5c9420 chore: fix some typos (#1370)
• f3b51be Fix #1375: untyped tuple deconstruction statements are assignments (#1377)
• c4199f7 dedupe sourcify runner artifact names (#1373)
• 3e402d2 Make the IR builder tolerant to parse errors (#1359)
• b35d0b5 [npm] Bump cspell from 8.19.3 to 9.1.2 (#1367)
• a37cac1 [cargo] Bump the non-major-dependencies group with 6 updates (#1369)
• df6695e More efficient Sourcify CI workflows (#1348)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by omartawfik, a new releaser for @​nomicfoundation/slang since your current version.

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)