[fpc-pascal] Generic type conflicts

Ben Grasset operator97 at gmail.com
Wed Nov 6 15:43:28 CET 2019

On Wed, Nov 6, 2019 at 2:01 AM Sven Barth via fpc-pascal <
fpc-pascal at lists.freepascal.org> wrote:

> A normal if-statements has the same non-evaluation.

Not in the way I meant, though.

Like, I thought the difference between "normal if" and "ternary if" was
supposed to be the same as the difference between the existing IfThen()
function and the intrinsic version of IfThen(), on which you based the
"if-then-else" syntax I think.

By which I mean, something similar to the difference between "if" and
"static if" in the D programming language (at least when given things that
are possible to evaluate at compile time, like GetTypeKind is in Pascal).
For example:

import std.stdio;
import std.traits;

// Would not compile, because everything is evaluated fully,
// and in this case the parameters we pass aren't
// compatible with all branches.
void PrintSomething(T)(T value) {
  if (isFloatingPoint!(T)) {
    writefln("Floating point value: %f", value * value);
  } else if (isIntegral!(T)) {
    writefln("Integral value: %d", value * value);
  } else if (isSomeString!(T)) {
    writefln("String value: %s", value ~ value);

// Compiles fine, as only the relevant branch for
// a given parameter is evaluated.
void StaticPrintSomething(T)(T value) {
  static if (isFloatingPoint!(T)) {
    writefln("Floating point value: %f", value * value);
  else static if (isIntegral!(T)) {
    writefln("Integral value: %d", value * value);
  else static if (isSomeString!(T)) {
    // "~" does string concatenation in D
    writefln("String value: %s", value ~ value ~ value);

void main() {

The point being that the type-checking is neither useful or necessary in
scenarios where the branch being evaluated is statically known to be
unreachable ahead of time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-pascal/attachments/20191106/112972ab/attachment.html>

More information about the fpc-pascal mailing list