v1.4.0 Visual improvement

Compare with previous
On this release;

NameETABetterVisual() method has been added. Just like NameETA() method, this method use eTATimeInMs as input parameter and returns string result. NameETA() method was optimized for high-CPU-intense algorithm therefore it returns string as (x minute(s) and y second(s)) format which might not look the best. NameETABetterVisual() method checks output data and returns as "1 minute and 2 seconds" NameETABetterVisual() could be used when output data needs better readability.

First and second tabs use NameETA(), third and fourth tab use NameETABetterVisual()

v1.3.0 Unsafe methods

Compare with v1.0.0
On this release;

Methods that use int data type as index or totalIndex value were limited due to int data type's max limit. Uint data types are now supported to increase this range.
Unsafe methods are now available to use. Unsafe methods are technically unsafe to use but due to removing of control mechanism on parameters they increase performance on high CPU-intensity applications.
Logical unsafe methods are now available to use. Logical unsafe methods are logically unsafe, technically safe methods. Removing of control mechanism on methods may increase performance on high CPU-intensity applications.