Owen Avery
Owen Avery
Should this type of thing be caught at the beginning of type checking, end of name resolution, or a separate phase like `CfgStrip`?
TLDR, it looks like you can override functions with functions that return a different type, *if* you're not overriding a virtual function https://godbolt.org/z/TW1rjbMba ```c++ #include class A { public: std::unique_ptr...
The "^^^" comment was supposed to be a reply to https://github.com/Rust-GCC/gccrs/pull/3799#discussion_r2098520527
We could use deducing-this to great effect here, but that's a C++23 thing (GCC 14)
Looks like auto-merge didn't work
> > There are changes required here i think we can get away wit this check but not totally convinced yet > > Also it will need to be applied...
Would probably be good to make `lvalue_p` operate on HIR nodes instead of trees
> I don't know if this is the best way to go about this, it's definitely hacky. maybe we could do all the desugars as part of the fixed point...
> > I don't know if this is the best way to go about this, it's definitely hacky. maybe we could do all the desugars as part of the fixed...
@CohenArthur @P-E-P