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

refactor: untangle data flow structs #412

Merged
merged 7 commits into from
Apr 2, 2024

Conversation

macklin-10x
Copy link
Contributor

Works over the type hierarchy used to pass high-level data around, removing redundancy and tightening up mutation.

@@ -60,8 +32,6 @@ pub struct EncloneExacts {
pub join_info: Vec<JoinInfo>,
pub drefs: Vec<DonorReferenceItem>,
pub sr: Vec<Vec<Double>>,
pub fate: Vec<HashMap<String, BarcodeFate>>, // GETS MODIFIED SUBSEQUENTLY
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not any more, it doesn't! :)

Base automatically changed from macklin/clean-up-print-clonotypes to main March 28, 2024 02:59
@macklin-10x macklin-10x force-pushed the macklin/untangle-data-flow-structs branch from b124b0d to d25b9b9 Compare March 28, 2024 03:06
Copy link
Contributor

@sreenathkrishnan sreenathkrishnan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice simplification!

Comment on lines +258 to +261
// The original logic for computing this value was based on the confusing
// assumption that this is always true if self.tcr is false.
// I've preserved this for now, but this line might make sense to add:
// assert!(self.bcr);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense! We could use enum instead of two booleans

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the logic here was just so odd/implicit that I decided to back away slowly before turning and running

@macklin-10x macklin-10x merged commit 3759c79 into main Apr 2, 2024
2 checks passed
@macklin-10x macklin-10x deleted the macklin/untangle-data-flow-structs branch April 2, 2024 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants