sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Problems with `ChatVariablesService#attachContext`
Labels: important,debt,chat

There is couple of issues and code smell with `attachContext`

https://github.com/microsoft/vscode/blob/f70bf1770392659e863f682cd23a31c2161bee37/src/vs/workbench/contrib/chat/browser/chatVariables.ts#L165-L189

* it checks for the `ChatLocation` - something that we have gotten past since a while
* it uses the last focused widget which can very well be of another `ChatLocation`
* it opens the chat panel (`showChatView`) if it finds no other widget - this is really awkward and bad

IMO instead the method should just be called with a target widget
Repository: go
Issue: net/http: ServeMux.Handler does not populate named path wildcards
Labels: NeedsInvestigation

### Go version

go version devel go1.24-b17a55d095 Tue Sep 24 23:20:50 2024 +0000 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/chressie/.cache/go-build'
GOENV='/home/chressie/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/chressie/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/chressie/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/chressie/src/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/chressie/src/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.24-b17a55d095 Tue Sep 24 23:20:50 2024 +0000'
GODEBUG=''
GOTELEMETRY='on'
GOTELEMETRYDIR='/home/chressie/.config/go/telemetry'
GCCGO='/usr/bin/gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/chressie/src/go/src/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build549655017=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

The [http.ServeMux.Handler](https://pkg.go.dev/net/http#ServeMux.Handler) method currently [discards patterns and matches](https://cs.opensource.google/go/go/+/refs/tags/go1.23.1:src/net/http/server.go;l=2577;drc=773767def0e0f29584a69bd760430167b7479d7d) that findHandler returns.

This behavior makes it impossible to use named path wildcards in http.Handler implementations that want to use an http.ServeMux as the underlying request multiplexer.

The following program shows a common pattern that demonstrates this:

```
package main

import (
	"fmt"
	"net"
	"net/http"
	"time"
)

func main() {
	mux := http.NewServeMux()
	mux.HandleFunc("/{foo}", func(w http.ResponseWriter, r *http.Request) {
		fmt.Printf("handler1: {foo}==%q\n", r.PathValue("foo"))
	})
	mux.HandleFunc("/x/{bar}", func(w http.ResponseWriter, r *http.Request) {
		fmt.Printf("handler2: {bar}==%q\n", r.PathValue("bar"))
	})

	// Typical middleware that routes all requests to mux.
	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		h, _ := mux.Handler(r)
		h.ServeHTTP(w, r)
	})

	ln, _ := net.Listen("tcp", ":0")
	go (&http.Server{Handler: http.DefaultServeMux, Addr: ln.Addr().String()}).Serve(ln)
	http.Get("http://" + ln.Addr().String() + "/wildcard-foo")
	http.Get("http://" + ln.Addr().String() + "/x/wildcard-bar")
}
```




### What did you see happen?

Executing above program yields

```
% go run t.go
handler1: {foo}==""
handler2: {bar}==""
```

The wildcards were not populated.

### What did you expect to see?

I'd expect to see the wildcards populated.

```
% go run t.go
handler1: {foo}=="wildcard-foo"
handler2: {bar}=="wildcard-bar"
```
Repository: tauri
Issue: [feat] Webview Window Focusable Property
Labels: type: feature request

### Describe the problem

There isn't the ability to create a window that is not focusable, like a onscreen keyboard. Electron has a BaseWindow property that can be set of focusable which then causes the window never to gain focus.

### Describe the solution you'd like

This would be a property that is set on the WebviewWindow which will define if the window can take focus or not. The window should still be interactable with the user.

### Alternatives considered

I have attempted to create the window and change the window style with WinApi but have not been successful in changing the styles. As I don't always know where the focus has come from I cannot always just give it back with a event when the focus is gained in the window.

### Additional context

_No response_
Repository: transformers
Issue: Refactor `output_hidden_states` to allow index selection
Labels: Feature request,Vision

### Feature request


Models such as Llava use CLIPVision with `output_hidden_states=True` then select the index of `hidden_states` that it needs e.g. `image_outputs.hidden_states[vision_feature_layer]`.

`output_hidden_states` could be refactored to `output_hidden_states: Optional[Union[bool, int]] = None` and `hidden_states` output changed to `hidden_states: Optional[Union[torch.FloatTensor, Tuple[torch.FloatTensor, ...]]] = None`.

The layer index would need to be normalized to account for negative index:
```python
if type(output_hidden_states) is int and output_hidden_states < 0:
    output_hidden_states = min(len(self.layers), len(self.layers) + output_hidden_states + 1) # or config.num_hidden_layers
```

`CLIPEncoder` could be changed from
```python
for idx, encoder_layer in enumerate(self.layers):
    if output_hidden_states:
        encoder_states = encoder_states + (hidden_states,)
```
to
```python
for idx, encoder_layer in enumerate(self.layers):
    if type(output_hidden_states) is int and output_hidden_states == idx:
        encoder_states = hidden_states
    elif output_hidden_states:
        encoder_states = encoder_states + (hidden_states,)
```
and after the loop changed from
```python
if output_hidden_states:
    encoder_states = encoder_states + (hidden_states,)
```
to
```python
if type(output_hidden_states) is int and output_hidden_states == len(self.layers):
    encoder_states = hidden_states
elif output_hidden_states:
    encoder_states = encoder_states + (hidden_states,)
```

Models such as Llava would then be able to do:
```python
image_outputs = self.vision_tower(pixel_values, output_hidden_states=vision_feature_layer)
selected_image_feature = image_outputs.hidden_states
```

### Motivation

Memory efficiency, as per the [comment](https://github.com/huggingface/transformers/blob/68049b17a6bb4c9b0d499e9e77121effa2f5a6c0/src/transformers/models/llava/modeling_llava.py#L454) in Llava `"this is not memory efficient at all (output_hidden_states=True) will save all the hidden stated."`

This would also improve memory efficiency in CLIP Text, specifically in Diffusers pipelines such as Stable Diffusion XL where the penultimate layer is used or when `clip skip` is used.


### Your contribution

I can submit a PR.
Repository: angular
Issue: DeepSignal Inputs and Models
Labels: area: core,core: reactivity,cross-cutting: signals

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Currently, Angular's signal-based inputs and models work well for primitive types, but they become cumbersome when dealing with complex objects. This feature request proposes the implementation of "DeepSignal" inputs and models, which would provide a more convenient way to work with nested properties in objects, especially in scenarios involving two-way binding and forms.

The main benefits of this feature would be:

- Easier listening to specific properties of complex objects without the need for additional computeds or equality checks.
- Simplified template usage for nested properties.
- More convenient handling of forms and filters with multiple fields.
- Improved developer experience when working with complex data structures.

### Proposed solution

Introduce two new functions: deepInput() and deepModel(), which would create DeepSignal instances. These would behave similarly to the existing input() and model() functions but with enhanced capabilities for nested properties.

Example usage:
``` 
@Component({...})
export class MyComponent {
  filterParams = deepInput<{param1: string, param2: string}>();
  viewModel = deepModel<{name: string, password: string}>();
}
```

In the template:
```
{{ filterParams.param2() }}
<input type="text" [(ngModel)]="viewModel.name">
```

The DeepSignal type would need to be writable to support two-way binding scenarios.

This solution would be particularly beneficial in views with multiple filters, selections, and inputs, allowing developers to work with a single object rather than individual signals for each property. For example:

```
interface SomeProps {
    dateRange: { start: Date, end: Date },
    category: string,
    searchTerm: string,
    isActive: boolean
}
@Component({...})
export class FilterComponent {
  filters = deepInput<SomeProps>();
} 
```
This approach simplifies handling complex filter objects without creating separate inputs for each property.

### Alternatives considered

1. Using computed signals for each nested property: This approach works but leads to verbose code and doesn't solve the two-way binding issue elegantly.
2. Creating custom operators or utility functions: While this could provide similar functionality, it wouldn't be as seamless as having built-in support in Angular.

By implementing DeepSignal inputs and models, we can significantly improve the developer experience when working with complex objects in Angular applications, especially in scenarios involving forms and filtering.
Repository: go
Issue: x/tools/gopls: document Rename package feature
Labels: Documentation,gopls,Tools

See:
- https://github.com/golang/go/issues/69582
Repository: pytorch
Issue: torch.unique does not keep order of occurences even with "sorted=False"
Labels: triaged,module: python frontend

### 🐛 Describe the bug

Hello, 

Thank you for the awesome package. I recently noticed that torch.unique does not keep the order of occurences even with sorted argument set to False.

Please is there a temporary work around for this?

Please can this be implemented in future release? it is a very important feature for some applications where order matter.



### Versions

$ python collect_env.py
Collecting environment information...
PyTorch version: 2.4.0+cu118
Is debug build: False
CUDA used to build PyTorch: 11.8
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 11 Pro
GCC version: (x86_64-posix-seh-rev0, Built by MinGW-Builds project) 13.2.0
Clang version: Could not collect
CMake version: version 3.28.3
Libc version: N/A

Python version: 3.9.16 (main, May 17 2023, 17:49:16) [MSC v.1916 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.22631-SP0
Is CUDA available: True
CUDA runtime version: 11.2.67
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 2080 Ti
Nvidia driver version: 535.98
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture=9
CurrentClockSpeed=2500
DeviceID=CPU0
Family=205
L2CacheSize=11776
L2CacheSpeed=
Manufacturer=GenuineIntel
MaxClockSpeed=2500
Name=13th Gen Intel(R) Core(TM) i5-13500
ProcessorType=3
Revision=

Versions of relevant libraries:
[pip3] numpy==1.26.3
[pip3] torch==2.4.0+cu118
[pip3] torch_geometric==2.4.0
[pip3] torchaudio==2.4.0+cu118
[pip3] torchvision==0.19.0+cu118
[conda] libblas 3.9.0 8_mkl conda-forge
[conda] libcblas 3.9.0 8_mkl conda-forge
[conda] liblapack 3.9.0 8_mkl conda-forge
[conda] mkl 2020.4 hb70f87d_311 conda-forge
[conda] numpy 1.24.4 pypi_0 pypi
[conda] torch 2.0.1+cu117 pypi_0 pypi
[conda] torch-geometric 2.4.0 pypi_0 pypi
[conda] torchaudio 2.0.2+cu117 pypi_0 pypi
[conda] torchvision 0.15.2+cu117 pypi_0 pypi

cc @albanD
Repository: ant-design
Issue: Clicking on tooltip changes the visibility of Collapse Item 
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-yxbuhh?file=demo.tsx)

### Steps to reproduce

1. Hover on Collapse label
2. Click on tooltip

### What is expected?

The collapse shouldn't change it's state on clicking on tooltip

### What is actually happening?

The collapse is getting closed/ opened.

| Environment | Info |
| --- | --- |
| antd | 5.14.2 |
| React | 18.3.1 |
| System | MacOS |
| Browser | Chrome -  129.0.6668.59 |

---
I tried e.stopPropagation() for onClick of Tooltip, but the onClick is not exposed for Tooltip component. Exposing the same can be a possible fix.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Second "Files have been modified on disk" dialog not focused
Labels: bug,topic:editor,needs testing,topic:gui

### Tested versions

4.x

### System information

Godot v4.3.stable - macOS 13.0.1 - Vulkan (Mobile) - integrated Apple M1 - Apple M1 (8 Threads)

### Issue description

When reloading a project that has changed on disk, two "Files have been modified on disk" dialogs are generated rather than one; and the second is not focused, requiring an extra click to clear it.

You can repro this just by `touch`ing files in a terminal, but in practice I run into this every time I change git branches via the terminal.

### Steps to reproduce

1. Open a project in Godot.
2. Open 2 scenes and 2 scripts in the editor.
3. In a terminal, `touch` those .tscn and .gd files.
4. Switch back to Godot.
5. Two "Files have been modified on disk" popups appear on top of each other - one for scripts, and one for scenes and settings files.
6. Mouse-click "Discard" in the topmost popup.

**Expected behavior:**
The second popup is focused, so you can click "Discard" in that as well to get back to work.

**Actual behavior:**
The Godot window is focused, and the second popup (blocking the godot window) is blurred.  You must click once to focus it, and then you can click "Discard".

**An even better expected behavior:**
The two dialogs are merged into one containing all changed files, so a single "Discard" click dismisses them all.

### Minimal reproduction project (MRP)

Anything with at least two scenes and two scripts.
Repository: electron
Issue: [Bug]: Switching between two views back and forth will flicker.
Labels: platform/macOS,bug :beetle:,status/confirmed,has-repro-gist,33-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

33.0.0-beta.3

### What operating system(s) are you using?

macOS

### Operating System Version

macOS Sonoma 14.6.1 (23G93)

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

Don't flicker when switching between views.

### Actual Behavior

Switching between two views back and forth will flicker.


### Testcase Gist URL

https://gist.github.com/code-small-white/76438ffb2a4a7bb6e297ad8ce67f3240

### Additional Information

```js
mainWindow.contentView.addChildView(a)
mainWindow.contentView.removeChildView(b)
```
- Using the above approach, flickering still happens.
Repository: go
Issue: x/tools/gopls: usePlaceholders=false disables variable name suggestions when using the var! suffix completion 
Labels: gopls,Tools,gopls/completion

### gopls version

golang.org/x/tools/gopls v0.16.1

### go env

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/urandom/.cache/go-build'
GOENV='/home/urandom/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/urandom/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/urandom/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/lib/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.1'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/urandom/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build4155953414=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

I've disabled the `usePlaceholders` option, since having it enabled inserts invalid syntax, causing more work.

Then I attempted to complete a `.var!` suffix completion on a function call, in order to have the variables defined.

### What did you see happen?

`,  := theFunctionThatWasCompleted()`

### What did you expect to see?

`someVar, err := theFunctionThatWasCompleted()`

### Editor and settings

Zed:
```
  "lsp": {
    "gopls": {
      "initialization_options": {
        "usePlaceholders": false
      }
    }
  },
```

### Logs

_No response_
Repository: TypeScript
Issue: Allow `satisfies` in string enum member initializers
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

satisfies, enum

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

I suggest that TypeScript should allow this:

```ts
enum Foo {
  Foo = "Foo" satisfies "Foo"
}
```

Currently this is treated as a computed enum member and requires `number` type, despite nothing being actually computed here.

### 📃 Motivating Example

With `isolatedModules`/`isolatedDeclarations` enabled references in enum members are restricted. For example, this does not compile with `isolatedDeclarations`:

```ts
const FOO = "Foo"

enum Foo { Foo = FOO }
// Error: Enum member initializers must be computable without references to external symbols with --isolatedDeclarations.
```

`satisfies` here will ensure that `Foo` is properly typed while not referring to external symbols:

```ts
const FOO = "Foo"

enum Foo { Foo = "Foo" satisfies typeof FOO }
```

### 💻 Use Cases

See motivating example above.
Repository: deno
Issue: Uncaught Error: Not implemented: Pipe.prototype.listen - Windows
Labels: bug,node compat

Version: Deno 2.0.0-rc.5 (release candidate, release, x86_64-pc-windows-msvc)

When I run `deno run -A .\node_modules\nx\bin\nx.js serve projectName` 

I get the following error

```
detached processes are not currently supported on Windows
detached processes are not currently supported on Windows
detached processes are not currently supported on Windows
errorerror: : Uncaught Error: Not implemented: Pipe.prototype.listen - Windows
    at notImplemented (ext:deno_node/_utils.ts:9:9)
    at Pipe.listen (ext:deno_node/internal_binding/pipe_wrap.ts:144:7)
    at Server._setupListenHandle [as _listen2] (node:net:1178:28)
    at _listenInCluster (node:net:1012:12)
    at Server.listen (node:net:1278:7)
    at Object.<anonymous> (file:///<HOME>/deno-2-test/node_modules/.deno/nx@19.7.4/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker.js:146:8)
    at Object.<anonymous> (file:///<HOME>/deno-2-test/node_modules/.deno/nx@19.7.4/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker.js:160:4)
    at Module._compile (node:module:748:34)
    at Object.Module._extensions..js (node:module:767:10)
    at Module.load (node:module:665:32)Uncaught Error: Not implemented: Pipe.prototype.listen - Windows
    at notImplemented (ext:deno_node/_utils.ts:9:9)
    at Pipe.listen (ext:deno_node/internal_binding/pipe_wrap.ts:144:7)
    at Server._setupListenHandle [as _listen2] (node:net:1178:28)
    at _listenInCluster (node:net:1012:12)
    at Server.listen (node:net:1278:7)
    at Object.<anonymous> (file:///<HOME>/deno-2-test/node_modules/.deno/nx@19.7.4/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker.js:146:8)
    at Object.<anonymous> (file:///<HOME>/deno-2-test/node_modules/.deno/nx@19.7.4/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker.js:160:4)
    at Module._compile (node:module:748:34)
    at Object.Module._extensions..js (node:module:767:10)
    at Module.load (node:module:665:32)

error: Uncaught Error: Not implemented: Pipe.prototype.listen - Windows
    at notImplemented (ext:deno_node/_utils.ts:9:9)
    at Pipe.listen (ext:deno_node/internal_binding/pipe_wrap.ts:144:7)
    at Server._setupListenHandle [as _listen2] (node:net:1178:28)
    at _listenInCluster (node:net:1012:12)
    at Server.listen (node:net:1278:7)
    at Object.<anonymous> (file:///<HOME>/deno-2-test/node_modules/.deno/nx@19.7.4/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker.js:146:8)
    at Object.<anonymous> (file:///<HOME>/deno-2-test/node_modules/.deno/nx@19.7.4/node_modules/nx/src/project-graph/plugins/isolation/plugin-worker.js:160:4)
    at Module._compile (node:module:748:34)
    at Object.Module._extensions..js (node:module:767:10)
    at Module.load (node:module:665:32)

 NX   Failed to start plugin worker.
```

Is that a compatibility issue, a nx issue or a windows issue?
Repository: rust
Issue: "downstream crates may implement trait for type" for both trait and type private to this crate
Labels: C-enhancement,T-compiler,D-incorrect,A-coherence

```
$ rustc --version
rustc 1.83.0-nightly (363ae4188 2024-09-24)
```


```rust
use std::cmp::Ordering;
use compare::Compare;
use num_cmp::NumCmp;

trait PartialCompare<L: ?Sized, R: ?Sized = L> {
    fn compare(&self, l: &L, r: &R) -> Option<Ordering>;
}

impl<L, R, C: Compare<L, R>> PartialCompare<L, R> for C {
    fn compare(&self, l: &L, r: &R) -> Option<Ordering> {
        Some(self.compare(l, r))
    }
}

#[derive(Default, Debug, Clone, Copy)]
struct NumCompare;

impl<L, R> PartialCompare<L, R> for NumCompare
where
    L: NumCmp<R> + Copy,
    R: Copy,
{
    fn compare(&self, l: &L, r: &R) -> Option<Ordering> {
        NumCmp::num_cmp(*l, *r)
    }
}


fn main() {}
```

With dependencies:

```toml
num-cmp = "0.1.0"
compare = "0.1.0"
```

Failed to compile:

```
error[E0119]: conflicting implementations of trait `PartialCompare<_, _>` for type `NumCompare`
  --> src/main.rs:18:1
   |
9  |   impl<L, R, C: Compare<L, R>> PartialCompare<L, R> for C {
   |   ------------------------------------------------------- first implementation here
...
18 | / impl<L, R> PartialCompare<L, R> for NumCompare
19 | | where
20 | |     L: NumCmp<R> + Copy,
21 | |     R: Copy,
   | |____________^ conflicting implementation for `NumCompare`
   |
   = note: downstream crates may implement trait `compare::Compare<_, _>` for type `NumCompare`
```

Since both `PartialCompare` and `NumCompare` are defined in this crate, the error message seems incorrect. Not sure it's a bug or an error messaging inaccurate.