same, well not that exact plush but this one :) https://edunham.net/2016/04/11/plushie_rustacean_pattern.html
#5BCEFA at (7,9)
Palette and y-coordinate helper
- Cyan - #5BCEFA at 7-10, 23-26
- Pink - #F5A9B8 at 11-14, 19-22
- White - #FFFFFF at 15-18
#5BCEFA at (6,8)
Palette and y-coordinate helper
- Cyan - #5BCEFA at 7-10, 23-26
- Pink - #F5A9B8 at 11-14, 19-22
- White - #FFFFFF at 15-18
#F5A9B8 at (4,13)
Palette and y-coordinate helper
- Cyan - #5BCEFA at 7-10, 23-26
- Pink - #F5A9B8 at 11-14, 19-22
- White - #FFFFFF at 15-18
#F5A9B8 at (4,12)
imma just pretend the pink above this one is the right shade xD
Palette and y-coordinate helper
- Cyan - #5BCEFA at 7-10, 23-26
- Pink - #F5A9B8 at 11-14, 19-22
- White - #FFFFFF at 15-18
#5BCEFA at (4,10)
Palette and y-coordinate helper
- Cyan - #5BCEFA at 7-10, 23-26
- Pink - #F5A9B8 at 11-14, 19-22
- White - #FFFFFF at 15-18
#5BCEFA at (4,9)
Palette and y-coordinate helper
- Cyan - #5BCEFA at 7-10, 23-26
- Pink - #F5A9B8 at 11-14, 19-22
- White - #FFFFFF at 15-18
#5BCEFA at (3,24)
Palette and y-coordinate helper
- Cyan - #5BCEFA at 7-10, 23-26
- Pink - #F5A9B8 at 11-14, 19-22
- White - #FFFFFF at 15-18
PR: Merged
Good call with using a shared reference so now we can kiss our partner(s) more than once!!
Kissing many partners with one big smooch might be hard tho, maybe we need to change the implementation to use combinatorics so that everyone kisses each of their partners at least once.
Since there's no way to tell who kisses who, i can cheat by printing nCr times :3
pub fn lovers(partners: &[&dyn Gender]) {
match partners.len() {
0 => {
println!("ghost smooch~");
}
1 => {
println!("mirror smooch~");
}
p => {
// p >= 2, safe to unwrap
for _ in 0..ncr(p, 2).unwrap() {
println!("smooch~");
}
}
}
}
pub trait Gender {}
// implement your own gender, and if u want, publish online! :3
pub struct Masculine;
impl Gender for Masculine {}
pub struct Feminine;
impl Gender for Feminine {}
// removed old api:
// fn two_lovers(one: Masculine, two: Feminine)
// srry not srry for breaking backwards compat
// new version has more flexible api!<3
fn two_lovers(one: Box<dyn Gender>, two: Box<dyn Gender>) {
println!("smooch~");
}
// todo: other functions!!
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn me_and_who() {
two_lovers(Box::new(Feminine), Box::new(Feminine));
}
}
Someone can correct me if im wrong but I think nullable in C# still doesnt force you to do a null check before accessing properties or methods, however I believe it does give a type error when using a nullable type where non-nullable is expected, which is good. So it might not be 1-to-1 but it fulfills a similar purpose for sure.
Coming from a rust background I would have sure appreciated my workplace enabling the nullable feature on our main codebase from the start. I've run out of patience for null errors :(
#5BCEFA at (5,9)
Palette and y-coordinate helper