Re: Vibe.d Password Verification

2025-02-05 Thread Adam Wilson via Digitalmars-d-learn
On Wednesday, 5 February 2025 at 15:16:10 UTC, seany wrote: Is there any built in passowrd verification for Vibe.d? Such as bcrypt.verifypassword(password , hash)? I looked at this library: https://code.dlang.org/packages/passwd This is causing linking error ( ld: error: unable to find library

Re: help with prime pairs code

2025-02-05 Thread Jabari Zakiya via Digitalmars-d-learn
On Tuesday, 4 February 2025 at 17:17:42 UTC, Jabari Zakiya wrote: On Monday, 3 February 2025 at 04:59:43 UTC, monkyyy wrote: On Monday, 3 February 2025 at 04:15:09 UTC, Jabari Zakiya wrote: I translated this Ruby code: FYI. This code finds all the prime pairs that sum to n for all even in

Re: Vibe.d Password Verification

2025-02-05 Thread Jonathan M Davis via Digitalmars-d-learn
On Wednesday, February 5, 2025 8:16:10 AM MST seany via Digitalmars-d-learn wrote: > Is there any built in passowrd verification for Vibe.d? Such as > bcrypt.verifypassword(password , hash)? > > I looked at this library: https://code.dlang.org/packages/passwd > This is causing linking error ( ld:

Re: Vibe.d Password Verification

2025-02-05 Thread Sergey via Digitalmars-d-learn
On Wednesday, 5 February 2025 at 15:16:10 UTC, seany wrote: Any help would be appreciated. My password is being sent as string over a secure https connection. The hash is stored as another string. There are also these 2: https://code.dlang.org/packages/dauth https://code.dlang.org/packages/a

Vibe.d Password Verification

2025-02-05 Thread seany via Digitalmars-d-learn
Is there any built in passowrd verification for Vibe.d? Such as bcrypt.verifypassword(password , hash)? I looked at this library: https://code.dlang.org/packages/passwd This is causing linking error ( ld: error: unable to find library -lbsd) - yes i am on FreeBSD with my hoster. I can't change

Re: interface inference with delegates/functions

2025-02-05 Thread axricard via Digitalmars-d-learn
On Wednesday, 5 February 2025 at 01:20:07 UTC, Jonathan M Davis wrote: Note that it talks about the "initial inferred return type", whereas your function doesn't have an initial inferred return type, because it fails to compile when determining the return type. So, while the spec doesn't expand