Cecile Tonglet  

@CecileTonglet

Ex-CTO | Now helping to build Web 3 | Proud Internet rando | 🦀 Rustacean

Vrijeme pridruživanja: svibanj 2014.

Tweetovi

Blokirali ste korisnika/cu @CecileTonglet

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @CecileTonglet

  1. Prikvačeni tweet

    Finally released my second blog post! 🤗 About the importance of empowering your team & the motivation that comes with it

    Poništi
  2. proslijedio/la je Tweet
    prije 6 sati
    Poništi
  3. proslijedio/la je Tweet
    prije 19 sati

    Rust compiler performance is hard to have meaningful discussions about because: (1) There’s no single part of the compiler which is slow. In fact the compiler is pretty well optimized.

    Prikaži ovu nit
    Poništi
  4. proslijedio/la je Tweet
    prije 19 sati

    Newish to parenting reckons.. the lack of diverse gender roles in children's books is really disappointing. Maybe there's more to being a woman than being a princess who needs to be saved?

    Poništi
  5. *cargo git update (not cargo update)

    Prikaži ovu nit
    Poništi
  6. cargo git delete <branch> To delete a branch and its remote/upstream branch in one go.

    Prikaži ovu nit
    Poništi
  7. Another useful thing: cargo git squash This will soft reset your branch to the parent branch. It's like doing a rebase and squashing everything. This is useful when you want to write the proper commit message before merging.

    Prikaži ovu nit
    Poništi
  8. When you want to visualize your work: cargo git diff This runs the `git diff` command but only on files that are not Cargo.lock. When you want to stage changes: cargo git add Just like git add, but it will ignore Cargo.lock. All the git add options are available (like -p)

    Prikaži ovu nit
    Poništi
  9. Another cool feature: cargo git update --deps This will not touch at your current Git state. Run `cargo update`. And make a commit with just Cargo.lock. Any changes (stages or not) are kept, no need to stash or anything.

    Prikaži ovu nit
    Poništi
  10. The main advantage is also that you solve conflicts commit-per-commit like a rebase but without being in a rebase state. And you solve them from bottom to top. The update command will try to update as much as possible without your intervention.

    Prikaži ovu nit
    Poništi
  11. That's my new workflow. It doesn't use rebase at all and it has the advantage to keep the commits in their original order. Of course it is expected that you squash merge at the end and not merge (otherwise you will have a lot of WIP in master)

    Prikaži ovu nit
    Poništi
  12. 4. You update your branch with master: cargo update This will try to merge as much as possible without conflict. 5. If there is a conflict, the command will stop like a git merge. You resolve and commit. 6. Run again: cargo git update (Run again until it's up-to-date)

    Prikaži ovu nit
    Poništi
  13. In brief: 1. You create new branches using: cargo git fork my-new-branch origin/master (You want the parent to be origin/master, not just master) 2. (add changes) 3. You commit with: cargo git commit (This will create a WIP, no need to put a commit message for now)

    Prikaži ovu nit
    Poništi
  14. I finished all the commands of my new cargo-git. A Git helper to use with 's cargo. I should make a video or a demo to show how this workflow works but you could use it for some specific helpers and keep your own workflow

    Prikaži ovu nit
    Poništi
  15. 1. velj

    I finished the base for my git nuk.. I mean, git merge command. When it merges, it automatically destroys your local branch and the branch on the upstream ☢️ use it with care!!

    Poništi
  16. proslijedio/la je Tweet
    1. velj
    Odgovor korisniku/ci

    For each consecutive argument in a function I indent 2.5 spaces. Ending braces are indented an amount of spaces equal to the line distance from the start brace - brilliant for visualising the amount of lines in a block.

    Poništi
  17. 31. sij

    I'm already using the cargo git diff in place of my cargo diff. Now when I press F10 or F11 on my terminal I don't have the huge Cargo.lock showing up anymore

    Prikaži ovu nit
    Poništi
  18. 31. sij

    I think about integrating 's cargo-scout to this tool. So you don't need to add git-hooks

    Prikaži ovu nit
    Poništi
  19. 31. sij

    Most common annoying thing: "expected type somecrate::error::Error, got ()" and when you copy-paste it, it says "module somecrate::error is private" and it is actually in somecrate::Error

    Prikaži ovu nit
    Poništi
  20. 31. sij

    It would be great if rustc displayed the actual importable name of types in the compiler messages. Most of the time I just want to copy-paste them but I can't because the type is behind a private module or it is already imported but uses an alias

    Prikaži ovu nit
    Poništi
  21. 30. sij

    Happy birthday! .... I mean, every time these is a release it feels like a great event with lot of surprise presents

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·