-
Notifications
You must be signed in to change notification settings - Fork 4
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
Conversation
@@ -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 |
There was a problem hiding this comment.
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! :)
b124b0d
to
d25b9b9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice simplification!
// 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); |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
Works over the type hierarchy used to pass high-level data around, removing redundancy and tightening up mutation.