nickva opened a new pull request, #6038:
URL: https://github.com/apache/couchdb/pull/6038

   OTP 27-29 are aready the only versions tested in CI so we don't test 26 any 
longer and it's gone out of support.
   
   We can take advantage of OTP 27+ with some of these features:
   
   * Tripple quotes strings
   
   ```
       J = """
           {"a":"b"}
           """
   ```
   
   Nice for json blobs
   
   * Sigils. Nice for binaries.
   
   ```
   B = ~"a binary"
   ```
   
   * `maybe` is always enabled
   
   * New json module. Jiffy is faster but for small and quick command line 
scripts it may be nice to not have to load a NIF
   
   * Process labels
   
   `proc_lib:set_label({client_proc, IP})`
   
   Then we can filter by that and or see them in observer and other debug tools.
   
   * ets:first_lookup/ets:next_lookup
   
   Traverse ets tables easier
   
   <!-- Thank you for your contribution!
   
        Please file this form by replacing the Markdown comments
        with your text. If a section needs no action - remove it.
   
        Also remember, that CouchDB uses the Review-Then-Commit (RTC) model
        of code collaboration. Positive feedback is represented +1 from 
committers
        and negative is a -1. The -1 also means veto, and needs to be addressed
        to proceed. Once there are no objections, the PR can be merged by a
        CouchDB committer.
   
        See: http://couchdb.apache.org/bylaws.html#decisions for more info.
   
        Artificial Intelligence and Large Language Models Contributions Policy
   
        It is expressly forbidden to contribute material generated by
        AI, LLMs, and similar technologies, to the CouchDB project. 
        This includes, but is not limited to, source code, documentation,
        commit messages, or any other areas of the project.
   
   -->
   
   ## Overview
   
   <!-- Please give a short brief for the pull request,
        what problem it solves or how it makes things better. -->
   
   ## Testing recommendations
   
   <!-- Describe how we can test your changes.
        Does it provide any behaviour that the end users
        could notice? -->
   
   ## Related Issues or Pull Requests
   
   <!-- If your changes affect multiple components in different
        repositories please put links to those issues or pull requests here.  
-->
   
   ## Checklist
   
   - [ ] This is my own work, I did not use AI, LLM's or similar technology
   - [ ] Code is written and works correctly
   - [ ] Changes are covered by tests
   - [ ] Any new configurable parameters are documented in 
`rel/overlay/etc/default.ini`
   - [ ] Documentation changes were made in the `src/docs` folder
   - [ ] Documentation changes were backported (separated PR) to affected 
branches
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to