Iterator support in the RPC binding generator #1014

New issue

Open

opened 2025-12-28 17:14:56 +00:00 by sami · 2 comments

sami commented

2025-12-28 17:14:56 +00:00

Owner

Originally created by @roman-khimov on GitHub (Oct 27, 2022).

On one hand it's pretty simple, any InteropInterface{} return item can be treated as an iterator by default (other types are very rare), but on the other we have no idea what's the type of an individual iterator element. Even #2767 doesn't help a lot without additional annotations.

Originally created by @roman-khimov on GitHub (Oct 27, 2022). On one hand it's pretty simple, any `InteropInterface{}` return item can be treated as an iterator by default (other types are very rare), but on the other we have no idea what's the type of an individual iterator element. Even #2767 doesn't help a lot without additional annotations.

sami added the

feature

compiler

rpc

labels

2025-12-28 17:14:56 +00:00

sami commented

2025-12-28 17:14:56 +00:00

Author

Owner

@roman-khimov commented on GitHub (Dec 8, 2022):

Something like storage.Find(..., returnValue interface{}) with type derived from returnValue can help in absence of generics (#2376).

@roman-khimov commented on GitHub (Dec 8, 2022): Something like `storage.Find(..., returnValue interface{})` with type derived from `returnValue` can help in absence of generics (#2376).

sami commented

2025-12-28 17:14:56 +00:00

Author

Owner

@roman-khimov commented on GitHub (Sep 18, 2023):

Generics can fix it easily though.

@roman-khimov commented on GitHub (Sep 18, 2023): Generics can fix it easily though.