Ensures a given expression of type Char is a literal with a valid value according to a given validation function.
Ensures a given expression of type Char is a literal with a valid value according to a given validation function.
If the given Char expression is a literal whose value satisfies the given validation function, this method will
return normally. Otherwise, if the given Char expression is not a literal, this method will complete abruptly with
an exception whose detail message includes the String passed as notLiteralMsg. Otherwise, the
given Char expression is a literal that does not satisfy the given validation function, so this method will
complete abruptly with an exception whose detail message includes the String passed as notValidMsg.
This method is intended to be invoked at compile time from macros. When called from a macro, exceptions thrown by this method will result in compiler errors. The detail message of the thrown exception will appear as the compiler error message.
the compiler context for this assertion
the Char expression to validate
a String message to include in the exception thrown if the expression is a literal, but not valid
a String message to include in the exception thrown if the expression is not a literal
a function used to validate a literal value parsed from the given expression
Ensures a given expression of type Double is a literal with a valid value according to a given validation function.
Ensures a given expression of type Double is a literal with a valid value according to a given validation function.
If the given Double expression is a literal whose value satisfies the given validation function, this method will
return normally. Otherwise, if the given Double expression is not a literal, this method will complete abruptly with
an exception whose detail message includes the String passed as notLiteralMsg. Otherwise, the
given Double expression is a literal that does not satisfy the given validation function, so this method will
complete abruptly with an exception whose detail message includes the String passed as notValidMsg.
This method is intended to be invoked at compile time from macros. When called from a macro, exceptions thrown by this method will result in compiler errors. The detail message of the thrown exception will appear as the compiler error message.
the compiler context for this assertion
the Double expression to validate
a String message to include in the exception thrown if the expression is a literal, but not valid
a String message to include in the exception thrown if the expression is not a literal
a function used to validate a literal value parsed from the given expression
Ensures a given expression of type Float is a literal with a valid value according to a given validation function.
Ensures a given expression of type Float is a literal with a valid value according to a given validation function.
If the given Float expression is a literal whose value satisfies the given validation function, this method will
return normally. Otherwise, if the given Float expression is not a literal, this method will complete abruptly with
an exception whose detail message includes the String passed as notLiteralMsg. Otherwise, the
given Float expression is a literal that does not satisfy the given validation function, so this method will
complete abruptly with an exception whose detail message includes the String passed as notValidMsg.
This method is intended to be invoked at compile time from macros. When called from a macro, exceptions thrown by this method will result in compiler errors. The detail message of the thrown exception will appear as the compiler error message.
the compiler context for this assertion
the Float expression to validate
a String message to include in the exception thrown if the expression is a literal, but not valid
a String message to include in the exception thrown if the expression is not a literal
a function used to validate a literal value parsed from the given expression
Ensures a given expression of type Int is a literal with a valid value according to a given validation function.
Ensures a given expression of type Int is a literal with a valid value according to a given validation function.
If the given Int expression is a literal whose value satisfies the given validation function, this method will
return normally. Otherwise, if the given Int expression is not a literal, this method will complete abruptly with
an exception whose detail message includes the String passed as notLiteralMsg. Otherwise, the
given Int expression is a literal that does not satisfy the given validation function, so this method will
complete abruptly with an exception whose detail message includes the String passed as notValidMsg.
This method is intended to be invoked at compile time from macros. When called from a macro, exceptions thrown by this method will result in compiler errors. The detail message of the thrown exception will appear as the compiler error message.
the compiler context for this assertion
the Int expression to validate
a String message to include in the exception thrown if the expression is a literal, but not valid
a String message to include in the exception thrown if the expression is not a literal
a function used to validate a literal value parsed from the given expression
Ensures a given expression of type Long is a literal with a valid value according to a given validation function.
Ensures a given expression of type Long is a literal with a valid value according to a given validation function.
If the given Long expression is a literal whose value satisfies the given validation function, this method will
return normally. Otherwise, if the given Long expression is not a literal, this method will complete abruptly with
an exception whose detail message includes the String passed as notLiteralMsg. Otherwise, the
given Long expression is a literal that does not satisfy the given validation function, so this method will
complete abruptly with an exception whose detail message includes the String passed as notValidMsg.
This method is intended to be invoked at compile time from macros. When called from a macro, exceptions thrown by this method will result in compiler errors. The detail message of the thrown exception will appear as the compiler error message.
the compiler context for this assertion
the Long expression to validate
a String message to include in the exception thrown if the expression is a literal, but not valid
a String message to include in the exception thrown if the expression is not a literal
a function used to validate a literal value parsed from the given expression
Ensures a given expression of type String is a literal with a valid value according to a given validation function.
Ensures a given expression of type String is a literal with a valid value according to a given validation function.
If the given String expression is a literal whose value satisfies the given validation function, this method will
return normally. Otherwise, if the given String expression is not a literal, this method will complete abruptly with
an exception whose detail message includes the String passed as notLiteralMsg. Otherwise, the
given String expression is a literal that does not satisfy the given validation function, so this method will
complete abruptly with an exception whose detail message includes the String passed as notValidMsg.
This method is intended to be invoked at compile time from macros. When called from a macro, exceptions thrown by this method will result in compiler errors. The detail message of the thrown exception will appear as the compiler error message.
the compiler context for this assertion
the String expression to validate
a String message to include in the exception thrown if the expression is a literal, but not valid
a String message to include in the exception thrown if the expression is not a literal
a function used to validate a literal value parsed from the given expression
Trait providing assertion methods that can be called at compile time from macros to validate literals in source code.
The intent of
CompileTimeAssertionsis to make it easier to createAnyVals that restrict the values of types for which Scala supports literals:Int,Long,Float,Double,Char, andString. For example, if you are using odd integers in many places in your code, you might have validity checks scattered throughout your code. Here's an example of a method that both requires an oddIntis passed (as a precondition, and ensures an odd *Intis returned (as a postcondition):In either the precondition or postcondition check fails, an exception will be thrown at runtime. If you have many methods like this you may want to create a type to represent an odd
Int, so that the checking for validity errors is isolated in just one place. By using anAnyValyou can avoid boxing theInt, which may be more efficient. This might look like:An
AnyValcannot have any constructor code, so to ensure that anyIntpassed to theOddIntconstructor is actually odd, the constructor must be private. That way the only way to construct a newOddIntis via theapplyfactory method in theOddIntcompanion object, which can require that the value be odd. This design eliminates the need for placingrequireandensuringclauses anywhere else that oddInts are needed, because the type promises the constraint. ThenextOddmethod could, therefore, be rewritten as:Using the compile-time assertions provided by this trait, you can construct a factory method implemented vai a macro wthat causes a compile failure if
OddInt.applyis passed anything besides an oddIntliteral. ClassOddIntwould look exactly the same as before:In the companion object, however, the
applymethod would be implemented in terms of a macro. Because theapplymethod will only work with literals, you'll need a second method that can work an any expression of typeInt. Although you could write a factory method that throws a runtime exception if a non-oddIntis passed, we recommend afrommethod that returns anOption. The returnedOptioncan be processed to deal with the potential for non-odd values.The
applymethod refers to a macro implementation method in classPosIntMacro. The macro implementation of any such method can look very similar to this one. The only changes you'd need to make is theisValidmethod implementation and the text of the error messages.The
isValidmethod just takes the underlying type and returnstrueif it is valid, elsefalse. This method is placed here so the same valiation code can be used both in thefrommethod at runtime and theapplymacro at compile time. Theapplyactually does just two things. It calls aensureValidIntLiteral, performing a compile-time assertion that value passed toapplyis anIntliteral that is valid (in this case, odd). If the assertion fails,ensureValidIntLiteralwill complete abruptly with an exception that will contain an appropriate error message (one of the two you passed in) and cause a compiler error with that message. If the assertion succeeds,ensureValidIntLiteralwill just return normally. The next line of code will then execute. This line of code must construct an AST (abstract syntax tree) of code that will replace theOddInt.applyinvocation. We invoke the other factory method that returns anOption, and since we've proven at compile time that thatOptionwill be defined, we callgeton it.You may wish to use quasi-quotes instead of reify. The reason we use reify is that this also works on 2.10 without any additional plugin (i.e., you don't need macro paradise), and Scalactic supports 2.10.