Match statement: rid (documentation)

[topofocus]

According to the documentation, a MATCH-statement starts with "Match {type: ... [, as: ... ][, where: ... ] }"
If the rid is known, one ends with: "Match { type: the_database_type, where: ( @Rid = #1:0 ) }"

Surprisingly (for me) "Match { rid: #1:0 } " also works.

It seems, that "where: ( @Rid = #x:y ) } can generally substituted by "rid: #x:y"

My Question: Is it safe to use "rid: #x:y" in match queries, if yes: why is it missing in the documentation.

Thanks.
hartmut

[topofocus]

the answer seems to be related to a performance issue

 > d=Time.now;
   DB.query(" match { rid: #449:6  } .out('has_contract'){ type: option, as: o} return o.symbol " );
   d1=Time.now; 
   d1-d
 => 7.051627489
> d=Time.now;DB.query(" match { type: strategie, where: ( @rid= #449:6 ) } .out('has_contract'){ type: option, as: o} return o.symbol " );d1=Time.now; d1-d
 => 0.020200254
> d=Time.now;DB.query(" match { type: strategie, where: ( @rid= #449:6 ) } .out('has_contract'){ type: option, as: o} return o.symbol " );d1=Time.now; d1-d
 => 0.017033833

but

 > d=Time.now;
   DB.query(" match { type: strategie, rid:  #449:6  } 
              .out('has_contract'){ type: option, as: o} 
              return o.symbol " );
   d1=Time.now; 
   d1-d
 => 0.012890254

is the most efficient query

[lvca]

Confirm: lookup by RID is always faster and O(1)