-
Notifications
You must be signed in to change notification settings - Fork 437
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use a flow join instead of a sequence join for breadcrumbs when apply…
…ing tito Summary: As pointed out in D33037819 (5480bf6), we should almost always use `joined_breadcrumbs` instead of `accumulated_breadcrumbs`. The first will perform a "flow" join (i.e, may join always = may) between breadcrumbs from different callees, while the second one uses a "sequence" join (i.e, may join always = always). There are still a few places where we do use `accumulated_breadcrumbs`, i.e when gathering breadcrumbs from `AddFeaturesToArgument` or attribute models. Since those are user-specified, we want a sequence join instead of a flow join. Reviewed By: dkgi Differential Revision: D33488879 fbshipit-source-id: 312c8be77312b28345fc9a0fbe5f3fa44d639299
- Loading branch information
1 parent
d3012ee
commit 30c2fa4
Showing
3 changed files
with
3 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters