You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not really sure why the protein-translation exercise has an additional parse function that returns a pub struct CodonsInfo<'a>. It feels a bit weird to me. Maybe a better approach would be to model the codons as an enum?
The text was updated successfully, but these errors were encountered:
Looks like the exercise was added in this PR: #603.
There's no discussion on this design descision. It seems to me that it gives students the freedom to prepare the input data for efficient lookup (e.g. hash map), which can then be performed many times. (even though the test suite doesn't do that)
I'm sure the exercise could've been designed a different way, but is it worth it to break existing solutions?
I'm sure the exercise could've been designed a different way, but is it worth it to break existing solutions?
I don't think so. I just wanted to discuss some of the design decisions to maybe improve future exercises. I'll post a more detailed reply next week when I'm back at work!
I'm not really sure why the
protein-translation
exercise has an additionalparse
function that returns apub struct CodonsInfo<'a>
. It feels a bit weird to me. Maybe a better approach would be to model the codons as an enum?The text was updated successfully, but these errors were encountered: