-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Seed's UpdateEl::update method clashes with Itertools #370
Comments
Do you see any problems with the suggested solution? |
For fully qualified name syntax would perm fix but we might want to hold off for a bit. This is because I am getting some milage out of self implementing update to allow dx improvements. For instance the I'm thinking things like functions that set both style and inner node blocks (by returning a (Style, Node) typle) for a potential SeedUI. |
Ok, |
(can be implemented once #365 is resolved to prevent merge conflicts) |
This issue was just reported on Discord #support by user BestRanar . When using itertools and iterators in seed views that have not been terminated with a
collect::<Vec<_>>()
there is a disambiguation compiler error generated from the seed macro.Basically rust does not know whether to use Seed's
update
function or Itertools'supdate
.Probably the best bet to fix is to change the name of Seed's view macro
update()
method to something likeseed_update()
. The reason for this is that Seed'supdate
is internal to the seed macros and in theory not a public api and Itertools is common enough that this clash will come up more frequently.Another fix is to disambiguate directly in the seed macro, however this prevents implementation of custom UpdateEls by a user if needed.
The temporary fix to the above is to terminate iterators with a
collect()
if using itertools.The text was updated successfully, but these errors were encountered: