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
Doing a quick test here I found that this test pass.
#[test]
fn test_pow_u256() {
let five = U256::from((0, 0, 0, 5));
let two = U256::from((0, 0, 0, 2));
assert_eq(five, two);
}
Maybe it is the same problem as #4868 because I am seeing fn eq of U256 body empty at compile_fn. This is returning a const bool undef and wreaking havoc from there.
## Description
The issue was occurring because `get_items_for_type_and_trait_name` was
comparing an absolute call path to an external relative call path, when
the second should also be absolute.
`compile_fn` now checks if method is trait dummy.
These changes should avoid the silent failures where a dummy method is
used,
instead of the proper implementation.
Closes#4989
## Checklist
- [x] I have linked to any relevant issues.
- [x] I have commented my code, particularly in hard-to-understand
areas.
- [x] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).
- [x] I have added tests that prove my fix is effective or that my
feature works.
- [x] I have added (or requested a maintainer to add) the necessary
`Breaking*` or `New Feature` labels where relevant.
- [x] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [x] I have requested a review from the relevant team or maintainers.
Doing a quick test here I found that this test pass.
Maybe it is the same problem as #4868 because I am seeing
fn eq
ofU256
body empty atcompile_fn
. This is returning aconst bool undef
and wreaking havoc from there.Originally posted by @xunilrj in #4900 (comment)
The text was updated successfully, but these errors were encountered: