Ian Burton

The point of appending it into the slice in the first place is so Go has a reference and doesn't GC it while the C code is using it correct?...

Hey @pafuent , nice to get some confirmation on what I was observing. I noticed after posting that the original issue was related to #1492 that effected several people. I...

> We need to look at the original concept behind maxParam. I'd like to avoid introducing unsafe pointer arithmetics for working around a conceptional issue. Hi @lammel, my apologizes for...

Bit of an interesting development; my 404 issue has gone away this this, but instead of 404s now I get invalid contexts essentially. My unsafe code is honoring the original...

>If you end up setting a level that should not be logged, the level check won't be made and the even will be wrongly logged. I'm not sure I follow...

I had noticed [this bit of code](https://github.com/rs/zerolog/blob/791ca15d999a97768ffd3b040116f9f5a772661a/log.go#L437) prior. I was thinking I had to use NoLevel to get around that. However it seems like if I set LevelFieldName to the...

Hello all :wave: long time I got the notification that this had been closed @aldas , but don't see a commit that references a fix. Was this addressed in the...

Ah okay, so the suggestion is to use the workaround until v5. Thanks for the info! Edit: Though I do wonder, for those who don't know about this, if `echo.New`...

The original issue was simply about using the context method `SetParamNames` **at all** _specifically_ the race that could be caused [here](https://github.com/labstack/echo/blob/v4.1.17/context.go#L313) and [here](https://github.com/labstack/echo/blob/v4.1.17/context.go#L635). There wasn't any changing routes (on the...

Hey @aldas thanks for the replies I get what you're asking now. So originally (a few years ago now so the details are a bit fuzzy) I was updating an...