Closed timotheecour closed 6 years ago
This is actually not a glob issue it's the underlying regex
package. Could you move this over there?
Also it works if you declare pattern
as a const
rather than a let
.
Also it works if you declare pattern as a const rather than a let.
let
was intentional; eg if value known at runtime, not CT.
This is actually not a glob issue it's the underlying regex package. Could you move this over there?
just out of curiosity: do you know how much work (doesn't mean by "you" necessarily btw :) ) to use nre instead of nim-regex /cc @nitely
This is actually not a glob issue it's the underlying regex package. Could you move this over there?
indeed; done: https://github.com/nitely/nim-regex/issues/22
@timotheecour why would you prefer nre over nim-regex?
just out of curiosity: do you know how much work (doesn't mean by "you" necessarily btw :) ) to use nre instead of nim-regex
Use it for what, glob
? If so I think the API is different but the actual regex pattern syntax is probably the same.
why would you prefer nre over nim-regex?
I'm also curious about those reasons
why would you prefer nre over nim-regex? I'm also curious about those reasons
precisely the OP: allowing using regex at RT instead of CT; but it's all being sorted out ; it's possible with toPattern
and soon via re
too (see my PR https://github.com/nitely/nim-regex/pull/27)
it now works now that nitely/nim-regex#27 was merged; just edited OP
nre supports runtime regex, but not globEDIT: root cause is nim-regex