• Main website searches through sourcecode OR public services
• Dashboard searches through your services
• Docs search through docs

More importantly, almost all widgets look the same.

I think we need consistency here: either give all widgets the same functionality (dropdown for public services, sourcecode, your services, and docs) or change how they look. I think first option is ideal.

Checklist

Please ensure the following tasks are completed before filing a bug report.

• Read and understood the [Code of Conduct][code-of-conduct].
• Searched for existing issues and pull requests.

Description

Description of the issue.

The following code produces an array whose shape does not match what I'd expect:

CCList prints list contents within the provided start/stop strings without a box:

https://github.com/c-cube/ocaml-containers/blob/d34b7588b028f3618cc44d3f4c6417295db586c8/src/core/CCList.ml#L1821-L1823

which means that the indentation of list items doesn't take the start string's length into account, e.g.

[[`Binding ((Name "box")), 
`Rule 18, 
`Rule 20], ...]

If a box were

Somewhat related to #4.

Currently we have individual specification markdown documents for each module and we place them in the src/ directory.

Personally, I find that it'd be much easier to read the spec if we consolidated all the spec docs into a a single markdown file. Then we could have heading 2 for each module and heading 3 for each procedure. More importantly, if you wanted to show s

Just some ideas to reorganize the README in the docs.

• Put more useful info front & center - like what core modules we provide, and a brief explanation of what each module does
• move questions to a FAQ section (even though nobody is actually asking these questions)
• move other fluff content to an appropriate place (or delete)
• organize developer & contributor info in its own section

T

The readme gives an example usage of Set: Set.create(), but that gives me an error, "thx.Set has no field create". I looked instead at http://thx-lib.org/api/thx/Set.html and found Set.createInt(), Set.createString(), etc., which worked for me.

__sth__ for magic can't be used due to Nim's identifier syntax rules. However, anything easy to search-replace is fine as long as it wouldn't be a proper Python identifier anyway. How about syntax that is just a liitle magic in Nim too?

class OrderedDict(object):
  def `init`(self):
     ...

Also, modulo already uses this syntax in Nim so why not other operators, like add, let

Several modules in the stdlib have functions planned that have not yet been implemented.

Search for TODO in this codebase to find examples of them: https://github.com/gleam-lang/stdlib/search?q=TODO&unscoped_q=TODO

If you would like to help pick one and make a pull request with your implementation :)

Ideally one function per pull request so we can review quickly and easily.