tserg

this should have been fixed in 0.3.4: https://github.com/vyperlang/vyper/pull/2953

`_dynarray_make_setter` should store the length, and then use a helper to copy the body.

> this PR is shaping up, left a couple nits. thinking about whether we might want to move the dynarray method implementations into the builtins file as well? that would...

> looks like there is some code that is duplicated in structure. is there some way we can refactor `_validate_numeric_bounds` to address these cases? I have moved the typechecking to...

Note: We may want to add builtin constants for `MAX_UINT`, `MIN_INT` and `MAX_INT` for all integer types after this change. Otherwise, it is difficult to assign the min/max value in...

Seems like there is regression in bytecode size - e.g. ``` @external def foo() -> uint256: a: uint256 = 2 ** 200 b: uint256 = 5 return max(a, 5) +...

> Note: We may want to add builtin constants for `MAX_UINT`, `MIN_INT` and `MAX_INT` for all integer types after this change. Otherwise, it is difficult to assign the min/max value...

I am trying to reproduce this error. Can you help with the following? - Is the version correct? The https://github.com/vyperlang/vyper/commit/573d77f7af177fb3bf2be2a14d16e3b6c477a0fc commit should be running off `0.3.4`. - can you share...

I think injecting the `def supportsInterface(interface_id: bytes4) -> bool` function based on the `implements:` keyword can be confusing given Vyper's goal of simplicity. I have in mind someone starting out...

This also compiles, when it should not: ``` a: constant(uint16) = 200 b: constant(int248) = 100 @external def foo() -> int16: return a - b ```