# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 12
# self = https://watcher.sour.is/conv/3c2i2ia
Go 1.22.0 introduces a new experiment for range functions. Have you tried them out? What do you think it can make easier to accomplish?
The range function can signal when to stop running by returning false from the yield function.
The range function can signal when to stop running by returning false from the yield function.
the function can yield two values to include an index.
the function can yield two values to include an index.
I haven't tried it no😅
I haven't tried it no😅
I haven't tried it no😅
@xuu Oh, I wasn't aware of this! Thanks for bringing it to my attention.
I do like that they move away from one shared variable per loop to an own one per iteration. That makes sooo much more sense. I don't hit that often, but it happened a few times in the past and getting this figured out is not the easiest thing in the world.
I have to read up on the yield functions. From your examples I fear iterators would have been more useful. Let's see.
@xuu These are indeed iterators. Very weird syntax, though.
Things can get very interesting when we add the iter.Pull function in the mix. It works like pythons yield from.
Things can get very interesting when we add the iter.Pull function in the mix. It works like pythons yield from.