Semantics of the messages in expect
#2029
Closed
elBoberido
started this conversation in
General
Replies: 2 comments 1 reply
-
@elBoberido I would also prefer the rust semantics and would support this. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Created #2036 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In my last PR is described the actual expected result in the
expect
call of theexpected
andoptional
, e.g.This is okay since Foo is guaranteed
but I was made aware that in iceoryx it was mainly used to describe the unexpected outcome, e.g.Failed because Foo invariant is broken
. From my experience with Rust I'm more used to the former semantics, i.e. describe what is expected to happen. This can also be used instead of comments and as justification whyexpect
is called instead of doing some error handling.What do you think about changing the semantics of the
expect
message to describe why it is safe to callexpect
and also adjust the log output to something likeI would volunteer to change the current strings in iceoryx.
cc @elfenpiff @FerdinandSpitzschnueffler @mossmaurice @dkroenke @MatthiasKillat
Beta Was this translation helpful? Give feedback.
All reactions