[SUGGESTION] Don't accept implicit integers in [[assert: 1]]

[realgdman]

This is minor one.
When skimming through some snippets, I got impression that you can write
[[assert: 42]]
Which is actually not checking for value, (say, of short-syntax function), and just implicit converted to bool

According to this note at ES.87, checking for pointers is good, but checking integers without comparison can be suspicious.

Probably assert accepting only bools or pointers can be implemented with the help of concepts like std::is_arithmetic_v and std::is_pointer_v instead of simply bool

cppfront/include/cpp2util.h

Line 325 in f83ca9b

constexpr auto expects (bool b, CPP2_MESSAGE_PARAM msg = "" CPP2_SOURCE_LOCATION_PARAM_WITH_DEFAULT)

[JohelEGP]

We should still accept function pointers.

This is also valid: f: () [[pre: :() = 1]] = { }, https://godbolt.org/z/a7db78azx.

Generated C++1.

//=== Cpp2 type declarations ====================================================


#include "cpp2util.h"


//=== Cpp2 type definitions and function declarations ===========================

#line 1 "/app/main.cpp2"
auto f() -> void;
auto main() -> int;

//=== Cpp2 function definitions =================================================

#line 1 "/app/main.cpp2"
auto f() -> void{
                           cpp2::Default.expects([]() -> void { 1; }, "");
#line 1 "/app/main.cpp2"
}
auto main() -> int{}