2022-02-04 16:28:24 +00:00

43 lines
866 B
Plaintext

The return type ``++any++`` should be avoided because it prevents the type safety checks normally done by the compiler. When a function returns a primitive type (i.e. number, string or boolean) it is safe to replace ``++any++`` with ``++number++``, ``++string++`` or ``++boolean++`` type respectively, or remove the return type completely and let compiler infer it.
== Noncompliant Code Example
[source,javascript]
----
function foo() : any { // Noncompliant
return 1;
}
----
== Compliant Solution
[source,javascript]
----
function foo() {
return 1;
}
// or
function foo(): number {
return 1;
}
----
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
include::message.adoc[]
'''
== Comments And Links
(visible only on this page)
include::comments-and-links.adoc[]
endif::env-github,rspecator-view[]