add a future consideration

Author: cometkim

text/0001-int.md

@@ -117,6 +117,8 @@ let exponentiate = (x, y) => {
 
 ## API consideration
 
+TBD
+
 ## Questions
 
 ### Why do we even use `int`?
@@ -135,6 +137,12 @@ It is also for backward compatibility. Bounds-checking and failure early may be
 
 The `number | 0` is actually the most concise output form we can consistently use. Introducing any other runtime codes universally would lead to significant code bloat in the output.
 
+### Can we somehow make it match JavaScript's `number`?
+
+Perhaps in the future, we can make our number literals actually match JavaScript's number semantics. We could also rename `int` to `int32` and assign another literal like `0l`, as it was in OCaml syntax.
+
+However, this is not something that will happen in the near future. It won't occur until we are confident in our migration strategy to avoid breaking existing codebases. If done incorrectly, it could completely break compatibility with existing code.
+
 ## Future posibilities
 
 Guaranteeing the use of int32 types may offer additional advantages in the future when targeting WebAssembly or alternative native backends.