Lucas Trzesniewski

Results 82 comments of Lucas Trzesniewski

Note that you should use `'$(TargetFrameworkIdentifier)' == '.NETFramework'` to test if you're building for the .NET Framework, and this will also work with the old project format. Also, I didn't...

Thanks, I like the API :+1: Just one suggestion: maybe instead of an enum, what would you think about a class with column names as constants? ```C# public static class...

Hi @adamsitnik Yes, I know that 🙂 I wanted to compare the performance of `#if NETCOREAPP` blocks of code against `#else` blocks in the `Library` project on the *same runtime*,...

Well, we have the same use case actually 😄 Here's my solution, for reference: [the benchmark config](https://github.com/ltrzesniewski/pcre-net/blob/2d4c01f625e49ef0d6d9ad7f27f5d1ff236c3340/src/PCRE.NET.Benchmarks/Configs.cs#L7-L16), and [the library project settings](https://github.com/ltrzesniewski/pcre-net/blob/2d4c01f625e49ef0d6d9ad7f27f5d1ff236c3340/src/PCRE.NET/PCRE.NET.csproj#L4-L6). It's the same thing as in the original...

> Alternatively you could also disable Dependabot notifications in your settings. I haven't found such an option. There's an option to disable vulnerability alerts, but I'd still want to receive...

> Can this be turned into a single, very specific button? Sure, I like that approach. Might as well save a few clicks. 🙂 I'm just not sure about unsubscribe...

The main issue here is that PCRE.NET implemented string replacement before PCRE had this feature, and subsequently kept it. It doesn't use PCRE's substitution feature at all. The whole replacement...

> The tricky part is with more complex replacement strings It's not that tricky: ```C# PcreRegex.Replace("...", "...", m => $"{m["first"].Value.ToUpper()} and {m["second"].Value.ToUpper()} {m[3]}"); ``` > I guess one would have...

> if this repo ever explores an extended replacement grammar, my feeling is that it shouldn't be a "homegrown" flavor to fit both shoes, but a parallel track (alternative functions)...

> On an unrelated note: It seems the `$n` shorthand for referring to a capture group doesn't work? Using `$3` in place of `${3}` above just outputs `$3` verbatim. I...