And part 2

Why String and &str with comparisons to C ? ^^

[fiction] From C code with a lot of bugs to Rust with improvments

git merge-base branch1 branch2 will find the common ancestor commit of two branches.

Tip : check that only one commit is applied out of each command

git log branch1..common
git log branch2..common

• Cherry-pick the fix commit in a new branch (based on a common ancestor of the 2 branches) which will be then merged into them.
• Partial fix will be the same technique but the merge will be reverted in the feature branch before merging the feature branch in the master (see this)

Priority order :

• Importance
  1. transition
  2. !important
  3. animation
  4. normal rules
• Origin
  1. Website
  2. User
  3. Browser
• Specificity
  1. inline (within a style HTML property)
  2. id
  3. class | attribute | pseudo-class
  4. type | pseudo-element
• Position --> Order of the rules (rules defined later are first applied)

strace programm allow us to figure out what a program does under the hood.

Part 2 (x86 asm, linux kernel)
Part 3 (ftrace, disk layouts, ext4)

Solution : box the iterator and give the proper lifetime in signature function :

pub fn values<'a>(&'a self) -> Box<Iterator<Item = &i32> + 'a> {
        // ...
}

Thanks a lot for this post; it is much clearer in my mind.
And the explanation for the prelude module.

Covering Rust syntax and most used concept as fast as possible : that's great !

Avec la version en ligne

Les 3ères formes normales en base de données