sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Error in specialization type checking when using trait aliases
Labels: A-specialization,C-bug,F-trait_alias,requires-nightly,F-specialization


So I seem to have found an error in the type checking for specialization impls when using trait alias bounds

Specifically, this code:
```rust
#![feature(specialization)]
#![feature(trait_alias)]

pub trait Marker1<T> {}
pub trait Marker2 {}

pub trait CombinedMarker<T> = Marker1<T> + Marker2;

pub struct Container<T,U> { p: std::marker::PhantomData<(T,U)> }

pub struct Struct;
impl<T> Marker1<T> for Struct {}

pub trait Trait { fn do_thing(&self); }

impl<T, U:Marker1<T>> Trait for Container<T,U> {
    default fn do_thing(&self) { println!("default behavior"); }
}

impl<T, U:CombinedMarker<T>> Trait for Container<T,U> {
    default fn do_thing(&self) { println!("partially specialized behavior"); }
}

impl<T> Trait for Container<T,Struct> {
    fn do_thing(&self) { println!("fully specialized behavior") }
}
```
gives a type error with output of:
```
warning: the feature `specialization` is incomplete and may not be safe to use and/or cause compiler crashes
 --> src/main.rs:1:12
  |
1 | #![feature(specialization)]
  |            ^^^^^^^^^^^^^^
  |
  = note: `#[warn(incomplete_features)]` on by default
  = note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information

error[E0119]: conflicting implementations of trait `Trait` for type `Container<_, Struct>`:
  --> src/main.rs:51:1
   |
47 | impl<T, U:CombinedMarker<T>> Trait for Container<T,U> {
   | ----------------------------------------------------- first implementation here
...
51 | impl<T> Trait for Container<T,Struct> {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `Container<_, Struct>`

error: aborting due to previous error; 1 warning emitted

For more information about this error, try `rustc --explain E0119`.
```
_However_, if you change the bound on the `impl`s from `CombinedMarker<T>` to `Marker1<T>+Marker2` or `CombinedMarker<T>+Marker2` it actually compiles, seemingly suggesting that the compiler isn't accurately translating the trait alias over to the bound since all three of those _should_ be equivalent.

Also, before you ask, yes, for some reason, the `<T>` generic on `Marker1` _does_ seem to have an effect, as if it is removed, both the aliased and non-aliased versions compile. Furthermore, the `Container<T>` struct also seems to be important since removing it also fixed the type error.

Finally, for reference, my rustc is on this version:
```
rustc 1.47.0-nightly (6c8927b0c 2020-07-26)
binary: rustc
commit-hash: 6c8927b0cf80ceee19386026cf9d7fd4fd9d486f
commit-date: 2020-07-26
host: x86_64-unknown-linux-gnu
release: 1.47.0-nightly
LLVM version: 10.0
```
Repository: opencv
Issue: Build with Embarcadero Builder C++: Problem with " target feature 'mmx'"
Labels: priority: low,category: build/install

##### System information (version)
- OpenCV => 4.4.0
- Operating System / Platform => Windows 10 64 Bit
- Compiler => Embarcadero/Idera C++ RAD Studio 10.4, clang compiler bcc32c

##### Detailed description
During compiling I got the following (first) error:

```
[ 19%] Building CXX object modules/core/CMakeFiles/opencv_core.dir/src/arithm.cpp.obj
Embarcadero C++ 7.50 for Win32 Copyright (c) 2012-2020 Embarcadero Technologies, Inc.
D:\Di\Libraries\Packages\OpenCV\OpenCV440_Bcb104_32b_a\sources\modules\core\src\arithm.cpp:
In file included from D:\Di\Libraries\Packages\OpenCV\OpenCV440_Bcb104_32b_a\sources\modules\core\src\arithm.cpp:50:
In file included from D:\Di\Libraries\Packages\OpenCV\OpenCV440_Bcb104_32b_a\sources\modules\core\src/precomp.hpp:85:
In file included from D:/Di/Libraries/Packages/OpenCV/OpenCV440_Bcb104_32b_a/sources/modules/core/include\opencv2/core/hal/intrin.hpp:221:
D:/Di/Libraries/Packages/OpenCV/OpenCV440_Bcb104_32b_a/sources/modules/core/include\opencv2/core/hal/intrin_sse.hpp:1573:1: error:
      always_inline function '_mm_loadu_si128' requires target feature 'mmx', but would be inlined into function
      'v_load' that is compiled without support for 'mmx'
OPENCV_HAL_IMPL_SSE_LOADSTORE_INT_OP(v_uint8x16, uchar)
```

##### Steps to reproduce

1. cmake, disable almost everything, just build core
2. exchange the following files (2 problems already solved in a simple way, see [core.zip](https://github.com/opencv/opencv/files/4980089/core.zip)):
    - modules\core\include\opencv2\core\fast_math.hpp
    - modules\core\include\opencv2\core\hal\intrin.hpp
3. build to get error described above
4. whole output message of build. please see attached file 
[buildlog.txt](https://github.com/opencv/opencv/files/4980097/buildlog.txt)
Repository: ant-design
Issue: Table scroll to one designated Column
Labels: 💡 Feature Request,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
When edit a editable column, and the table is long enouph, that column can scroll to left, at least scroll to view.

### What does the proposed API look like?
scrollToColumn:columnIndex:number || columnDataIndex:string


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: iOS scrollbars should briefly show when page appears
Labels: platform-ios,framework,a: fidelity,f: scrolling,f: cupertino,c: proposal,P3,team-ios,triaged-ios

To match native iOS behaviour, scrollbars should briefly appear to indicate to the user that the content is scrollable.

You can see this behaviour in native iOS settings app:

<img src="https://user-images.githubusercontent.com/756862/88527120-84d22580-d005-11ea-8c27-cad8fd4e5db2.gif" width="300">

## Use case

When navigating to a new page, iOS has for as long as I remember (possibly since v1?) briefly flashed the scrollbar to the user can clearly see the content is overflowing and scrollable. It also gives a hint as to how much content is hidden.

## Proposal

When navigating to a new page, a primary scroll view with a `CupertinoScrollbar` should briefly show the scroll indicator. This should also happen when coming back from another page.

I'd argue scrollbars should do this by default, but developers should at least have a way of doing this.
Repository: react-native
Issue: Wrong button position when using KeyboardAvoidingView in combination with SafeAreaView and autofocus
Labels: Component: Button,Component: KeyboardAvoidingView,Component: SafeAreaView,API: Keyboard,Needs: Triage :mag:

## Description
I have an input with autoFocus, a SafeAreaView, and a KeyboardAvoidingView. However the Button which should have his position exactly above the keyboard gets some margin when using SafeAreaView in combination with autoFocus.

It is to mention that if I add a delay to autoFocus of around 250ms it is working as expected.

I've build an expo snack here: https://snack.expo.io/@simbob/keyboardavoidingview-bug

![safeareavie bug](https://i.stack.imgur.com/0uWIu.gif)

## React Native version:
```
react: ~16.11.0 => 16.11.0 
react-native: https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz => 0.62.2 
```

## Expected Results
Button should have the same position all time.

## Steps To Reproduce
```javascript
import React from "react";
import {
  StyleSheet,
  Text,
  View,
  TextInput,
  KeyboardAvoidingView,
  TouchableOpacity,
  Keyboard,
  SafeAreaView,
} from "react-native";

export default function App() {
  return (
    <SafeAreaView style={styles.container}>
      <KeyboardAvoidingView style={styles.container} behavior="padding">
        <View style={styles.top}>
          <Text>Open up App.js to start working on your app!</Text>
          <TextInput style={{ borderWidth: 1 }} autoFocus={true} />
        </View>
        <View style={styles.bottom}>
          <TouchableOpacity
            style={styles.loginScreenButton}
            onPress={Keyboard.dismiss}
          >
            <Text style={styles.loginText}>Blur</Text>
          </TouchableOpacity>
        </View>
      </KeyboardAvoidingView>
    </SafeAreaView>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    marginHorizontal: 16,
  },
  top: {
    flex: 0.7,
  },
  bottom: {
    flex: 0.3,
    justifyContent: "flex-end",
  },
  loginScreenButton: {
    paddingTop: 10,
    paddingBottom: 10,
    backgroundColor: "#1E6738",
    borderWidth: 1,
  },
  loginText: {
    color: "#fff",
    textAlign: "center",
  },
});
```
Repository: flutter
Issue: CupertinoTabBar should pop navigation stack when active tab tapped
Labels: platform-ios,framework,a: fidelity,f: cupertino,f: routes,c: proposal,P2,team-design,triaged-design

## Use case

To match native iOS behaviour, when tapping the active tab on a `CupertinoTabBar`, the associated `CupertinoTabView` should pop its navigator back to the root.

Here's an example from the App Store, where I tapped the "Apps" tab bar icon to navigate back:

<img src="https://user-images.githubusercontent.com/756862/88528890-e72c2580-d007-11ea-8572-d7eb19ef1a34.gif" width="300">

This also shows scrolling to top behaviour when tapping tab, see #62327.

## Proposal

1. User taps currently active `CupertinoTabBar` tab
2. Currently visible tab view navigation stack pops to root

If the currently visible page is the root page, it should scroll to the top, as per #62327.
Repository: flutter
Issue: CupertinoTabBar should scroll root page to top when tapped 
Labels: platform-ios,framework,a: fidelity,f: scrolling,f: cupertino,c: proposal,P3,team-ios,triaged-ios

## Use case

To match native iOS behaviour, when tapping an active `CupertinoTabBar` tab the current page should scroll to the top, as long as the current page is the root in the tab navigation stack.

Here's an example from the App Store, where I tapped the "Apps" tab bar icon to navigate back (see #62325), and then pressed it again to scroll the the top:

<img src="https://user-images.githubusercontent.com/756862/88528890-e72c2580-d007-11ea-8572-d7eb19ef1a34.gif" width="300">

## Proposal

1. User taps currently active `CupertinoTabBar` tab
2. If the page is the root in the navigation stack, the primary scrollview scrolls to the top.

If the page is not the root of the navigation stack, the stack should pop, see #62325.
Repository: scrcpy
Issue: Static build
Labels: help wanted,feature request

Hello crew,

Is there any plan to make it possible to  build a portable archive with all the dependencies for MacOS? that way, `scrcpy` can be integrated to other mac applications easily. (don't have to go steps like `brew install ffmpeg sdl2` to make it work).

Thanks,
Repository: angular
Issue: Allow lifecycle hooks to be defined on a directive instance and not only on a prototype
Labels: feature,area: core,core: lifecycle hooks,P3

We tend to get repeated requests for Angular to invoke lifecycle hooks defined on a directive / component instance (and not only ones defined on a prototype). Examples of such requests (actually, reported as bugs) would be #38043 or #38087 (but I'm sure that there are more as I've seen similar issues reported in the past.

To start with, the current Angular behaviour is the result of *deliberate design choices* and not a simple bug / omission that we can "just fix". The current design of taking lifecycle hooks from a prototype is based on the following:
* performance considerations;
* inheritance support.

### Performance considerations

As of today Angular assumes that all directives created from a given class have the same set of lifecycle functions (taken from a prototype). This assumptions allows us to make 2 significant optimisations:
* store lifecycle hooks only once for a given directive class, regardless of how many times it is instantiated (imagine a ngFor loop over hundreds of components / directives - as of today we need to store info about lifecycle hooks only one, regardless of the number of instances - if each instance could have different lifecycle hooks we would have to allocate memory for each instance, adding to GC pressure, consuming more memory and making the app slower overall);
* invoke lifecycle hooks on all instances without worrying about checking if a given hook exists - basically we _know_ that all components / directives share the same set so we can iterate over all instances and call hooks, without doing any checks.

Those things might sound like micr-optimisations but when you profile applications it has significant impact. Angular always worked this way as we made the assumption that the user experience (performance of a final app for the users) is more important that the developers experience here. 
 
### Inheritance

With the assumptions of a fixed set of lifecycle hooks for a directive it is easy for us to compute a new set of lifecycle hooks in the directives inheritance tree.  Again, we can do those calculations only once (per directive class), without checking each individual instance.

## Possible work-arrounds 

@petebacondarwin [suggested](https://github.com/angular/angular/issues/38043#issuecomment-663475929) that one might work-arround the current design choices like so:

```ts
@Component({selector: 'app-root', template: ''})
export class AppComponent {
  title = 'test-app';
}

(AppComponent.prototype as any).ngOnInit = () => {
  console.log('init!');
};
```

I'm opening this issue as a feature request, mostly to track interest and ideas for another implementation that wouldn't negatively impact performance.
Repository: go
Issue: compress/lzw: improve encoder performance with better hash function
Labels: NeedsDecision

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.2 windows/amd64
</pre>

### Does this issue reproduce with the latest release?
yes

### What did you do?
I found a CL from a long time ago, https://go-review.googlesource.com/c/go/+/123478, and the changes in it have greatly improved performance. But some of the work authors have not yet completed and disappeared. I want to resubmit the CL and complete the work for him, can I? Do you accept merge in this way?

@dsnet   @mdempsky
Repository: rust
Issue: Const functions sometimes don't do overflow checks in release mode
Labels: T-compiler,C-bug,A-const-eval

I tried this code in release mode:

```rust
const fn foo(arg: i32) -> i32 {
    arg + i32::MAX
}
const x: i32 = foo(1);
```

I expected to see this happen: `error: this arithmetic operation will overflow`

Instead, code successfully compiled.

If I replace `arg` with `1` in function than compilation failing with an overflow error.
Repository: youtube-dl
Issue: yespornplease.adult
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2020.06.16.1. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2020.06.16.1**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://yespornplease.adult/dyked-chanel-heart-misty-stone-sexy-lesbian-fucking/

## Description


Please add support for yespornplease.adult
Repository: rust
Issue: Improve documentation of read_vectored and write_vectored
Labels: C-enhancement,A-docs,T-libs

Apologies if this is a duplicate, but I couldn't find a mention of this anywhere.

A simple snippet like the following:

```rust
    let mut file = File::open("test.txt")?;

    let buffer = &mut [0u8; 6];
    let (mut first, mut second) = buffer.split_at_mut(3);
    let iovecs = &mut [IoSliceMut::new(&mut first), IoSliceMut::new(&mut second)];
    file.read_vectored(iovecs)?;
```

will incorrectly only populate the first `IoSliceMut` and exit prematurely on Windows. (See [here](https://gist.github.com/kubkon/29861a275b9ac6a762d1d6eed1c10984) for a full snippet).

See bytecodealliance/wasmtime#2070 for a downstream issue.
Repository: TypeScript
Issue: overload + generic + infer breaks conditional types
Labels: Bug

**TypeScript Version:** 3.9.2, 4.0.0-beta (playground), 3.9.6, 3.9.7 (locally tested)

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** overload generic conditional 

**Code**

```ts
type Wrap <T> = T & { wrap: T }
interface Data { id: number }
interface Foo {
    <K extends keyof Data> (): Wrap<Pick<Data, K>>;
    <K extends keyof Data> (): Wrap<Pick<Data, K>>;
}

type A = Foo extends (...args: any[]) => infer R ? 1 : 0;
type B = Foo extends (...args: any[]) => any ? 1 : 0;
declare let a: A, b: B;

a = b // Type '1' is not assignable to type '0'.(2322)
```

**Expected behavior:** compiles without error

**Actual behavior:** Type '1' is not assignable to type '0'

**Playground Link:** [Link](https://www.typescriptlang.org/play?ts=3.9.2#code/C4TwDgpgBA6gTgQzFAPAFQHxQLxTVAMigG8oB3RMALjygF8AoASwDtgI4AzBAY2gBEEwBCShMAJjRYBXALYAjDvWZsO3PlABiAe20kGUQ6gDSUCAA92LcQGcoAawghtnKIOFYAFAEoa8JCgACkw89ijuCAA0UMYYGADcBkYophZWtg5OLm5CCF6+sJRBIWER0bEJDIwMoJBQAII4WrpmlhDWdp4AdD0IcADmNjQILCAA2gC63jhYrJxKAEpQAPxQAIxQNAAMibXQAEJNOnpp7RndvQNDUCPjUzM3oyvrm1A7DOIQPAA2fdDfEGANxo9Wi8ho+0SDBEuHkDCAA)

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: godot
Issue: DynamicFont render issues when instanced.
Labels: bug,topic:rendering,topic:gui

**Godot version:**
Godot 3.2.2 stable, official.


**OS/device including version:**
Windows 10 (up to date), AMD Ryzen 3500U with Vega 8 graphics.


**Issue description:**
I'm building a small administrative "ecosystem", so I made a small "sdk" to share among a couple of projects. I have a base "button.tscn" which I use everywhere (I also have "label.tscn" and so on...). This base scenes all load "font_base.tres" as the custom font. I'm using the Ubuntu Light font.

Now, upon switching between scenes I get this:

![bug_1](https://user-images.githubusercontent.com/12116228/88554340-0452fb00-cfec-11ea-9906-db1eab500251.png)

If I render something on top of it:

![bug_2](https://user-images.githubusercontent.com/12116228/88554384-15037100-cfec-11ea-807e-0061127bcc99.png)

It gets fixed:

![bug_3](https://user-images.githubusercontent.com/12116228/88554447-251b5080-cfec-11ea-9d76-02cb5af4dee8.png)

As a test, I made a new custom font for a few instanced buttons (each of them, without saving the custom font to a file), and got proper rendering on the ones without the instanced custom font (all objects here are instanced):

![bug_4](https://user-images.githubusercontent.com/12116228/88555281-34e76480-cfed-11ea-9bec-a5fbb6de8a43.png)

This happens between 2 projects which use the same base files. All project settings are default and using the GLES2 driver. Sadly I don't know how to reproduce it in a new project.
Repository: pytorch
Issue: Slow `index_add_` on `torch.long` tensors 
Labels: module: performance,module: cuda,triaged

## 🐛 Bug

There is a significant performance drop when running `index_add_` on tensors of `torch.long`.

## To Reproduce

Run

```
import torch
import time

def test(dtype, N=60, niter=100): 
     x=torch.zeros(N, device='cuda',dtype=dtype) 
     idx=torch.randint(0,N, (1000000,), device='cuda', dtype=torch.long) 
     for i in range(niter): 
         x.index_add_(0,idx, torch.ones_like(idx, dtype=x.dtype)) 

# Warm-up run
test(torch.float32)
torch.cuda.synchronize(); 

# Experiment starts
for dtype in [torch.float32, torch.float64, torch.int32, torch.long]:
    s=time.time()
    test(dtype)
    torch.cuda.synchronize(); 
    print(f"{dtype}: {time.time()-s}s")
```

Output I get

```
torch.float32: 0.059488534927368164s
torch.float64: 0.042830705642700195s
torch.int32: 0.05532026290893555s
torch.int64: 1.3157131671905518s
```

where `torch.int64` is equivalent to `torch.long`.

## Expected behavior

The code with `torch.long` should run comparably fast.

## Environment
```
Collecting environment information...
PyTorch version: 1.5.0
Is debug build: No
CUDA used to build PyTorch: 10.2

OS: Ubuntu 20.04 LTS
GCC version: (Ubuntu 8.4.0-3ubuntu2) 8.4.0
CMake version: version 3.16.3

Python version: 3.8
Is CUDA available: Yes
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: GeForce GTX 1070
Nvidia driver version: 440.100
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.7.0.3
/usr/local/cuda-10.1/targets/x86_64-linux/lib/libcudnn.so.7.5.1

Versions of relevant libraries:
[pip3] mapillary-ai-research-pytorch==0.1.dev93+gfcc4396
[pip3] numpy==1.18.4
[pip3] torch==1.5.0
[pip3] torchvision==0.6.0
[conda] Could not collect

```


cc @VitalyFedyunin @ngimel
Repository: pytorch
Issue: Function names in title should not be capitalized in documentation
Labels: module: docs,triaged

## 📚 Documentation

In the API docs, the function names should NOT be capitalized. For example, in https://pytorch.org/docs/master/generated/torch.set_flush_denormal.html#torch.set_flush_denormal

we should not write

```
TORCH.SET_FLUSH_DENORMAL
```

but 

```
torch.set_flush_denormal
```

Python - like many other programming languages - is case sensitive.

cc @jlin27
Repository: opencv
Issue: could cv::cvtColor support CV_64F ?
Labels: category: imgproc,RFC

I am currently working with CV_32S images (accumulation of CV_16U astronomical images, overflowing the [0;65535] range)
When using cv::cvtColor on such images, I have to convert to CV_32F first, but naturally, some accuracy is lost by the CV32S->CV_32F conversion.
Is it reasonable that I work on a PR to support CV_64F in cv::cvtColor, or would it be rejected for not worthing the additional code ?

[edit]
"not worthing it" because most operations (RGB2GRAY, channels swap) can be performed by other means (cv::transform, cv::split/merge/mixChannels...); but I would prefer the unification behind cv::cvtColor