You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this bundling support typia.createIs<T>() can replace itself with the output function.
Howeover, the greatest support should be the addition of generic support for typia within macro calls. For instance, if the user has a macro function fetch:
export function fetch<T>() {
/// does some stuff
cont result: unknown = // ... use your imagination
const isResult = typia.is<T>(result);
if (isResult === false) throw 'wrong type`;
return result
}
In the example, fetch is itself a macro funtion, so for every use of it, it will be inlined and T can be known. Therefore, typia would gain support for use within generics in macros.
The text was updated successfully, but these errors were encountered:
I believe that typia should support "macros" as supported by the bun and parcel bundlers.
In this bundling support
typia.createIs<T>()
can replace itself with the output function.Howeover, the greatest support should be the addition of generic support for typia within macro calls. For instance, if the user has a macro function
fetch
:In the example,
fetch
is itself a macro funtion, so for every use of it, it will be inlined andT
can be known. Therefore, typia would gain support for use within generics in macros.The text was updated successfully, but these errors were encountered: