Expense proposal: Standardize `Text/replace` built-in

I would like to propose a $200 bounty for standardizing a new Text/replace built-in of type:

Text/replace : ∀(needle : Text) → ∀(replacement : Text) → ∀(haystack : Text) → Text 

Some relevant discussions include:

According to our expense guidelines, I need to formally document the following:

  • What purpose is the expense for?

    To standardize support for a Text/replace built-in as tracked in this issue

  • Is this a one-time or recurring expense?

    One-time

  • What is the amount you wish to expense?

    $200

For reference, our current project balance is $1,346.84

The expense is reviewed the same way we review changes to the language standard.

2 Likes

Should this get approved or not I’d be up for volunteering to try this. Haven’t standardised anything before, but I guess it’d involve updating similar files to say this PR https://github.com/dhall-lang/dhall-lang/pull/1062, and maybe the type inference docs/tests also?

If anyone else wants to jump in that’s cool, but thought I’d throw my name in the hat all the same.

1 Like

Alright, so this is approved according to the rules.

@alexhumphreys: Have at it! :slightly_smiling_face:

@Gabriel439 thanks! As you know I jumped the gun on this one and started early. But for anyone else who’s interested in this feature, here’s the link to the draft PR https://github.com/dhall-lang/dhall-lang/pull/1065

There’s a few open questions that some of ye may be interested in weighing in on :slight_smile: