You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common approach for writing stubs in Rust programming language is the todo! macro. First, it satisfies the type-checker and makes the code compileable. On the other hand, it calls a panic at runtime while printing the provided message.
fnfibonacci(n:usize) -> usize{if n == 0{0}else{todo!("I can't figure out how to implement it now")}}
So, if a project would like to use PDD during the development, it would be verbose since only three keywords are supported: @todo, TODO and TODO:. I suggest extending this amazing triplet with todo!.
todo!("#234:15m/DEV This is something to do later in one of the next releases.")}
instead of
// TODO #234:15m/DEV This is something to do later in one of the next releases.
todo!() }
As far as I know, @yegor256 does write in Rust, so I would like to hear an opinion from the project's founder.
The text was updated successfully, but these errors were encountered:
A common approach for writing stubs in Rust programming language is the
todo!
macro. First, it satisfies the type-checker and makes the code compileable. On the other hand, it calls a panic at runtime while printing the provided message.So, if a project would like to use PDD during the development, it would be verbose since only three keywords are supported:
@todo
,TODO
andTODO:
. I suggest extending this amazing triplet withtodo!
.instead of
As far as I know, @yegor256 does write in Rust, so I would like to hear an opinion from the project's founder.
The text was updated successfully, but these errors were encountered: