Update docs for compiletime error

Author: rtfpessoa

docs/docs/reference/metaprogramming/inline.md

@@ -383,12 +383,28 @@ The `error` method is used to produce user-defined compile errors during inline
 It has the following signature:
 
 ```scala
-inline def error(inline msg: String, objs: Any*): Nothing
+inline def error(inline msg: String): Nothing
 ```
 
 If an inline expansion results in a call `error(msgStr)` the compiler
 produces an error message containing the given `msgStr`.
 
+```scala
+inline def fail() = {
+  error("failed for a reason")
+}
+fail() // error: failed for a reason
+```
+
+or
+
+```scala
+inline def fail(p1: => Any) = {
+  error(code"failed on: $p1")
+}
+fail(indentity("foo")) // error: failed on: indentity("foo")
+```
+
 ## Implicit Matches
 
 It is foreseen that many areas of typelevel programming can be done with rewrite

library/src-3.x/scala/compiletime/package.scala

@@ -4,6 +4,17 @@ package object compiletime {
 
   erased def erasedValue[T]: T = ???
 
+  /** The error method is used to produce user-defined compile errors during inline expansion.
+   *  If an inline expansion results in a call error(msgStr) the compiler produces an error message containing the given msgStr.
+   *
+   *  ```scala
+   *  error("My error message")
+   *  ```
+   *  or
+   *  ```scala
+   *  error(code"My error of this code: ${println("foo")}")
+   *  ```
+   */
   inline def error(inline msg: String): Nothing = ???
 
   /** Returns the string representations for code passed in the interpolated values