Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
T
typon
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Analytics
Analytics
Repository
Value Stream
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
cython-plus
typon
Commits
c50615ef
Commit
c50615ef
authored
May 20, 2022
by
Xavier Thompson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
future.hpp: Use std::addressof consistently
parent
194d30eb
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
rt/include/typon/core/future.hpp
rt/include/typon/core/future.hpp
+4
-4
No files found.
rt/include/typon/core/future.hpp
View file @
c50615ef
...
...
@@ -31,7 +31,7 @@ namespace typon
if
(
ready
)
{
fdt
::
defer
defer
{
[
&
coroutine
]()
{
coroutine
.
destroy
();
}
};
std
::
construct_at
(
&
(
_result
),
coroutine
.
promise
().
get
());
std
::
construct_at
(
std
::
addressof
(
_result
),
coroutine
.
promise
().
get
());
}
else
{
...
...
@@ -68,7 +68,7 @@ namespace typon
{
if
(
!
_coroutine
)
{
std
::
destroy_at
(
&
(
_result
));
std
::
destroy_at
(
std
::
addressof
(
_result
));
}
}
...
...
@@ -151,7 +151,7 @@ namespace typon
if
(
ready
)
{
fdt
::
defer
defer
{
[
&
coroutine
]()
{
coroutine
.
destroy
();
}
};
std
::
construct_at
(
&
(
_result
),
coroutine
.
promise
().
get
());
std
::
construct_at
(
std
::
addressof
(
_result
),
coroutine
.
promise
().
get
());
}
else
{
...
...
@@ -166,7 +166,7 @@ namespace typon
{
if
(
!
_coroutine
)
{
std
::
destroy_at
(
&
(
_result
));
std
::
destroy_at
(
std
::
addressof
(
_result
));
}
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment