Curtis Vogt

I'll point out that IntervalSets.jl doesn't enforce this and they have strange outcomes when this occurs: ```julia julia> using IntervalSets julia> Interval(1, 3) ∩ Interval(2, 3) 2..3 julia> Interval(3, 1)...

That's interesting. I'd personally lean towards `parse(Int64, ...)` and `parse(Float64, ...)` not support whitespace

It isn't wildly used yet but there is: https://github.com/JuliaCI/PkgBenchmark.jl

> Currently the equality Day(1) == Second(86400) allows simplifying lots of operations. In the package [TimeZones.jl](https://github.com/JuliaTime/TimeZones.jl) this is not true as a day can be equal to Hour(23), Hour(24), or...

Note that `@NT(a,b)` is returning a type not a named tuple with the values of `a` and `b`: ```julia julia> typeof(@NT(a,b)) UnionAll julia> typeof(@NT(1,2.3)) NamedTuples._NT___1_____2__{Int64,Float64} ``` Note you can get...

If this feature were to be added we would probably need to separate the creation of named tuple types and instances to avoid additional confusion.

In #52 you can do: `NamedTuple{(:x, :y)}(1, 2)`. Does that seem better to you?

The plan from my perspective is to have NamedTuples.jl support both Julia 0.6 and 0.7 in a similar way to the [Missings.jl](https://github.com/JuliaData/Missings.jl) package. The PR #52 is an attempt to...

I've also noticed the problem with "Resource no accessible by integration" ``` Traceback (most recent call last): File "/root/tagbot/action/__main__.py", line 96, in repo.create_release(version, sha) File "/root/tagbot/action/repo.py", line 605, in create_release...

We can configure retries with PyGithub like in this example: https://github.com/PyGithub/PyGithub/issues/2759#issuecomment-1745643733