[Prototype design] [r1] happens on 5 days after [Prototype design]'s end [r2] happens on 5 days after [r1]'s end [r3] happens on 5 days after [r2]'s end [r2] displays on same row as [r1] [r3] displays on on same row as [r1] @endgantt 10.23 Highlight today @startgantt Project starts the 20th of september 2018 sunday are close 2018/09/21 to 2018/09/23 are colored in salmon 2018/09/21 to 2018/09/30 are named

[Prototype design] [r1] happens on 5 days after [Prototype design]'s end [r2] happens on 5 days after [r1]'s end [r3] happens on 5 days after [r2]'s end [r2] displays on same row as [r1] [r3] displays on on same row as [r1] @endgantt 10.23 Highlight today @startgantt Project starts the 20th of september 2018 sunday are close 2018/09/21 to 2018/09/23 are colored in salmon 2018/09/21 to 2018/09/30 are named

필요합니다: fn main() { let mut s = String::from("조심하세요!"); let r1 = &mut s as *mut String; let r2 = r1 as *const String; // Safe because r1 and r2 were obtained from references and so are // guaranteed other pointers. unsafe { println!("r1 은 {}입니다.", *r1); *r1 = String::from("이런"); println!("r2 는 {}입니다.", *r2); } // 안전하지 않음. 이렇게 하지 마세요. /* let r3: &String = unsafe { &*r1 }; drop(s); println!("r3 is: {}" 대부분의 경우 포인터는 align 되어 있어야 합니다. The ”NOT SAFE” section gives an example of a common kind of UB bug: *r1 has the 'static lifetime, so r3 has type &'static String, and thus outlives s. Creating a reference

필요합니다: fn main() { let mut s = String::from("조심하세요!"); let r1 = &mut s as *mut String; let r2 = r1 as *const String; // Safe because r1 and r2 were obtained from references and so are // guaranteed other pointers. unsafe { println!("r1 은 {}입니다.", *r1); *r1 = String::from("이런"); println!("r2 는 {}입니다.", *r2); } // 안전하지 않음. 이렇게 하지 마세요. /* let r3: &String = unsafe { &*r1 }; drop(s); println!("r3 is: {}" 대부분의 경우 포인터는 align 되어 있어야 합니다. The ”NOT SAFE” section gives an example of a common kind of UB bug: *r1 has the 'static lifetime, so r3 has type &'static String, and thus outlives s. Creating a reference

[Prototype design] [r1] happens on 5 days after [Prototype design]'s end [r2] happens on 5 days after [r1]'s end [r3] happens on 5 days after [r2]'s end [r2] displays on same row as [r1] [r3] displays on on same row as [r1] @endgantt 15.23 Highlight today @startgantt Project starts the 20th of september 2018 sunday are close 2018/09/21 to 2018/09/23 are colored in salmon 2018/09/21 to 2018/09/30 are named

[Prototype design] [r1] happens on 5 days after [Prototype design]'s end [r2] happens on 5 days after [r1]'s end [r3] happens on 5 days after [r2]'s end [r2] displays on same row as [r1] [r3] displays on on same row as [r1] @endgantt 16.23 Highlight today @startgantt Project starts the 20th of september 2018 sunday are close 2018/09/21 to 2018/09/23 are colored in salmon 2018/09/21 to 2018/09/30 are named

[Prototype design] [r1] happens on 5 days after [Prototype design]'s end [r2] happens on 5 days after [r1]'s end [r3] happens on 5 days after [r2]'s end [r2] displays on same row as [r1] [r3] displays on on same row as [r1] @endgantt 16.23 Highlight today @startgantt Project starts the 20th of september 2018 sunday are close 2018/09/21 to 2018/09/23 are colored in salmon 2018/09/21 to 2018/09/30 are named

[Prototype design] [r1] happens on 5 days after [Prototype design]'s end [r2] happens on 5 days after [r1]'s end [r3] happens on 5 days after [r2]'s end [r2] displays on same row as [r1] [r3] displays on on same row as [r1] @endgantt 16.29 Highlight today @startgantt Project starts the 20th of september 2018 sunday are close 2018/09/21 to 2018/09/23 are colored in salmon 2018/09/21 to 2018/09/30 are named