Matt W

I don't have a planned fix for this right now. The `processIncludes` routine is not very clever, but works under all versions of `node` without issue. It could be replaced...

Thinking about this over the weekend, you could try replacing the first regex at https://github.com/MatAtBread/nodent-runtime/blob/master/runtime.js#L35 with `\(\/\*[^*]*\*\/|\/\/[^\n]*)\` TBH, I don't have the same setup as you, so I don't have...

It's "stable", but at the time it was last updated, babel 7 was not. For me, it's in a maintenance phase (I don't use babel in my projects any more)....

For Babel v7.x.x install fast-async@7 - although I haven't used it for over a year when Babel7 was in beta - it's possible they've changed the plugin API since it...

@samchon , I think you're missing the point of the "Branding" - a technique that is used within the typescript compiler itself. Consider the types: ``` export type Brand =...

I understand your story. However, you've not answered the point: * Typescript provides a common way to protect against dev/compile time errors using branding. It is INTENDED to generate an...

Another way of looking at it is the `typia.tags.NoRuntimeCheck` is like the optional type marker you suggested, but ONLY at runtime, not dev/compile time

Dear Jeongho Nam, I have great respect for your technical capabilities. This is your project, and you should do as you see fit. But your comment `No matter how much...

Looking at the function `iterate_metadata_intersection`, validating `const x = Object.assign(123 as number /* not const */,{ u: 'u'});` above as: ``` console.log(typia.validate(x)) ``` ...works as expected (in a general sense...

I appreciate the extra insight. Perhaps we should ignore the "brand" case for now, and consider the `Object.assign(num,{ ...})` case, since that generates the correct type within TypeScript. This does...