Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variable resolution order, pronoun edition #136

Open
dgw opened this issue Jun 4, 2023 · 0 comments
Open

Variable resolution order, pronoun edition #136

dgw opened this issue Jun 4, 2023 · 0 comments
Labels

Comments

@dgw
Copy link
Collaborator

dgw commented Jun 4, 2023

There is a similar, but distinct, issue with variable resolution order like #63, which manifests when using e.g. both $who and $someone in the same tidbit. Pronoun vars like $heshe will always use the last value resolved, so in this example:

$who will grow to be very $adjective. $Heshe will $verb $adverb, and often.
However, their childhood friend $someone will intervene just in time, and
$heshe will marry the one who saved $himher.

$someone is resolved after $who, so all instances of $heshe, $himher, etc. will use $someone's gender, even the ones that occur in text before $someone. (In this case, even the ones after $someone also refer to $who, though.)

In a perfect world, Bucket would understand to which subject each $himher etc. refers and use the correct gender, but that's well beyond what processing currently happens to tidbits.

I don't think there's a simple way to solve this, which is probably why I put off opening an issue about it for so long, but users have been asking about it a fair bit recently so I wanted to have an easy link to reply with that explains the bug. 😅

@dgw dgw added the bug label Jun 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant