Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cours
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Programmation sysytème avancée
cours
Commits
1825f705
Verified
Commit
1825f705
authored
1 month ago
by
orestis.malaspin
Browse files
Options
Downloads
Patches
Plain Diff
added last slide
parent
cb553c55
No related branches found
No related tags found
No related merge requests found
Pipeline
#38991
passed
1 month ago
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
09_pinning.md
+20
-0
20 additions, 0 deletions
09_pinning.md
with
20 additions
and
0 deletions
09_pinning.md
+
20
−
0
View file @
1825f705
...
...
@@ -466,3 +466,23 @@ fn main() {
*
La macro
`pin!()`
nous sauve
*
Si on essaie de refaire l'exemple précent, on a une erreur de compilation
*
Si on veut absolument faire un
`Pin`
sur la pile, utiliser
`pin!()`
## La `Coroutine` et le pinning
*
Une souffrance infinie, mais en gros:
1.
Modofier
`poll()`
en
`poll(self: Pin<&mut self>)`
2.
Ajouter
`Pin<>`
autour de Task
3.
Ajouter un champs
`_pin: PhantomPinned`
à
`Coroutine`
*
Régler les problèmes du compilateur:
1.
Des
`as_mut()`
sur les
`match`
des future
2.
Ajouter un
`this = unsafe { self.get_uncheked_mut() }`
dans le
`poll()`
de
`HttpGetFuture`
*
Voilà
## En résumé
*
On a environ tout pour les
`Future`
en Rust
*
On a ajouté un moyen d'avoir un état interne à notre implémentation
`async/await`
*
On a ajouté un moyen d'enregistrer/charger des structures qui contiennent des références
*
On a vu le concept de
`Pin`
qui est fondamental pour garantir le modèle mémoire de Rust
*
Bref: actuellement on a un runtime primitif qui peut "tout" faire.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment