🐛 [Bug]: unsafeString2Bytes may not be future proof

[pjebs]

Bug Description

https://github.com/gofiber/fiber/blob/master/utils/convert.go#L24
https://github.com/gofiber/fiber/blob/master/internal/fasttemplate/unsafe.go#L15

See: https://stackoverflow.com/questions/59209493/how-to-use-unsafe-get-a-byte-slice-from-a-string-without-memory-copy

The current implementations may not be as future proof as it could be according to the discussion in the link above.

They propose:

func unsafeGetBytes(s string) []byte {
    if s == "" {
        return nil // or []byte{}
    }
    return (*[0x7fff0000]byte)(unsafe.Pointer(
        (*reflect.StringHeader)(unsafe.Pointer(&s)).Data),
    )[:len(s):len(s)]
}

How to Reproduce

N/A

Expected Behavior

N/A

Fiber Version

N/A

Code Snippet (optional)

No response

Checklist:

• I agree to follow Fiber's Code of Conduct.
• I have checked for existing issues that describe my problem prior to opening this one.
• I understand that improperly formatted bug reports may be closed without explanation.

[efectn]

Agree with you. I think we should use recommended solution.

[ReneWerner87]

The initial functions were copies of the fasthttp functions, we should open a topic there too

Furthermore we should comment the line with the magic limit and determine this number outside on a constant one