From Umar Getagazov to ~bouncepaw/betula
--- v1.0.0.myco | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v1.0.0.myco b/v1.0.0.myco index 04213f2..b9a11c6 100644 --- a/v1.0.0.myco +++ b/v1.0.0.myco @@ -21,7 +21,7 @@ See the [[installation.html | installation guide]]. If you are using any older r == Developers * [[https://links.bouncepaw.com | bouncepaw]] did most of the work. * [[https://links.handlerug.me | handlerug]] implemented the bookmarklet. * [[https://handlerug.me | handlerug]] implemented the bookmarklet.[message trimmed]
From Umar Getagazov to ~sircmpwn/sr.ht-dev
On Fri Jun 30, 2023 at 8:28 PM +03, Simon Ser wrote: > On Friday, June 30th, 2023 at 19:13, Umar Getagazov <umar@handlerug.me> wrote: > > On Fri Jun 30, 2023 at 8:11 PM +03, Simon Ser wrote: > > > Note, this means that the new pattern syntax will become part of our API. > > > > > > Looks fine to me. > > > > But it's not documented anywhere. Shouldn't it be treated the same as > > before? > > What do you mean? I'm not sure what you meant by "the new pattern syntax will become part of our API" if the only change is to the implementation, not
From Umar Getagazov to ~sircmpwn/sr.ht-dev
On Fri Jun 30, 2023 at 8:11 PM +03, Simon Ser wrote: > Note, this means that the new pattern syntax will become part of our API. > > Looks fine to me. But it's not documented anywhere. Shouldn't it be treated the same as before? Now thinking if glob should've been left as is and instead regular expression matching should've been added...
From Umar Getagazov to ~sircmpwn/sr.ht-dev
On Fri Jun 30, 2023 at 7:54 PM +03, Umar Getagazov wrote: > This is fully backwards-compatible, AFAIC. The only change the usage of > this library brings is the addition of '/**/'. Oh and this is somewhat incorrect, it also adds alternatives (e.g. "*.{txt,rtf,doc}" for matching "abc.txt", "abc.rtf", "abc.doc"). I don't think this is a huge deal, though.
From Umar Getagazov to ~sircmpwn/sr.ht-dev
This allows to use recursive patterns like "**/*.txt". Go's path.Match only allows explicit nesting, so to accomplish the same thing you'd need to duplicate the same pattern multiple times with different amount of asterisks ("*.txt", "*/*.txt", "*/*/*.txt"), depending on how deep your site's directory structure is. --- This is fully backwards-compatible, AFAIC. The only change the usage of this library brings is the addition of '/**/'. Changes since v1: - Fixed the library version (was unspecified i.e. v1, now v4) go.mod | 1 + go.sum | 2 ++ [message trimmed]
From Umar Getagazov to ~sircmpwn/sr.ht-dev
On Fri Jun 30, 2023 at 7:51 PM +03, Simon Ser wrote:
> This uses doublestar v1. We probably want to use the latest version, v4.
Damn, I think I ran go get with the correct version but then added an
import line without the version specified. Thanks for pointing this out,
will send a revision!
From Umar Getagazov to ~sircmpwn/sr.ht-dev
This allows to use recursive patterns like "**/*.txt". Go's path.Match only allows explicit nesting, so to accomplish the same thing you'd need to duplicate the same pattern multiple times with different amount of asterisks ("*.txt", "*/*.txt", "*/*/*.txt"), depending on how deep your site's directory structure is. --- This is fully backwards-compatible, AFAIC. The only change the usage of this library brings is the addition of '/**/'. go.mod | 1 + go.sum | 2 ++ graph/schema.resolvers.go | 3 ++- 3 files changed, 5 insertions(+), 1 deletion(-) [message trimmed]
From Umar Getagazov to ~sircmpwn/sr.ht-dev
The following changes since commit 992f33de3648bb6b1edae22e54cec8d2bf04da0b: api/graph: fix page-based profile pagination offset (2023-03-16 12:55:04 +0000) are available in the Git repository at: https://git.sr.ht/~handlerug/hire.sr.ht updates for you to fetch changes up to a9d7f9e3ce070e5adcefa9e5d783207dca5605a7: hiresrht: add a dashboard (2023-05-21 18:15:05 +0000) ---------------------------------------------------------------- Renato Torres (9):
From Umar Getagazov to ~sircmpwn/hare-dev
Signed-off-by: Umar Getagazov <umar@handlerug.me> --- Changes since v2: - Added "or their aliases" to clarify type_dereference's semantics language/expressions.tex | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/language/expressions.tex b/language/expressions.tex index 7f57d5e..a03f80d 100644 --- a/language/expressions.tex +++ b/language/expressions.tex @@ -2350,6 +2350,12 @@ Additionally, the implicit pointer type dereference semantics of \nonterminal{field-access-expression} and \nonterminal{indexing-expression} are [message trimmed]
From Umar Getagazov to ~sircmpwn/hare-dev
On Fri May 12, 2023 at 7:30 PM +03, Ember Sawady wrote: > type_dereference also dereferences aliases of pointer types, the only > reason we need the type_dealias is because we also want to dealias > non-pointer types. if this doesn't match the language currently used, we > should also update other places where type_dereference is mentioned in > the spec Hah, should've read the code. Well, can we rely on the reader to infer that "any number of non-nullable pointer types" includes type aliases of non-nullable pointer types? I'd say so.