NotANumber | An interactive blog on computer science and web dev 💡 | Blog library

First of all, the problem comes from the fact that JavaScript returns the type of NaN to be number. So maybe add additional check if the input is also not equal to NaN.

Like mentioned by Joakim Danielson and noted in the Apple Developer Documentation

... Because numeric types have different storage capabilities, attempting to initialize with a value of one type and access the value of another type may produce an erroneous result ...

And since Swift's Int struct cannot represent NaN values, you get this erroneous result.

Instead you could use Int's Failable Initialiser init(exactly:) that converts your NSDecimalNumber to an Int? that will either contain it's value or be nil if it is not representable by an Int.

The problem is that num_put only has a virtual do_put for double, not for float. So my float is silently casted to a double, losing my extended information.

The information is lost because the positions of the bits carrying it are different when the number is converted from float to double:

You can probably achieve this with a restriction

In Kotlin 1.0, the sealed functionality is rather restricted. For instance, all the subclasses must be nested, and a subclass can’t be made a data class ( data classes are covered later in this chapter). Kotlin 1.1 relaxes the restrictions and lets you define subclasses of sealed classes anywhere in the same file. In the given example, it is not allowed up until now. May be, in later release versions, they will relax this restriction. However, you can do this:

Ok so... not throwing any exception is the default choice of MOXy, the new default JAX-RS Json Provider for all Oracle products (Glassfish and WebLogic) (instead of Jackson). That seems strange to me... but yeah we have to deal with it :/

We have to register a ValidationErrorHandler for that purpose.

I found a complete (and working) solution right there: Custom MOXyJsonProvider in Jersey 2 not working?

Thanks to Jeroen Mostert for the hint that led me to this solution:

since two in you case is an input tag it doesn't have the innerHTML. Use value attribute instead. so it'll look like this:

Since it doesn't contain a significant value, the single instance of it can be reused everywhere. This saves you the creation cost of this object where you need it.

Another example of this would be Kotlin's Unit, which is also just an object.

This is just one of the examples of how you can avoid creating unnecessary instances that the garbage collector then has to clean up. Another example would be how the Java BigInteger class has final static fields for constants like ZERO and ONE. Although these do contain state, they are immutable, so they can be just one instance each that's reused and don't have to be re-created all the time.