sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: False warning regarding unsaved files
Labels: bug,info-needed,notebook-workbench-integration

### Applies To

- [x] Notebooks (.ipynb files)
- [ ] Interactive Window and\/or Cell Scripts (.py files with \#%% markers)

### What happened?

VS Code indicating that a file is unsaved when all files are actually saved.
It appear to only happen when Jupyter Notebooks are open.
![Image](https://github.com/user-attachments/assets/61340c1e-68e7-42c1-bcfb-1f0b6cc5004d)


### VS Code Version

1.96.0

### Jupyter Extension Version

2024.11.0

### Jupyter logs

```shell
N/A
```

### Coding Language and Runtime Version

Python v3.11.9  Jupyterlab v4.3.2 cupyter_core v5.72

### Language Extension Version (if applicable)

Python Extension

### Anaconda Version (if applicable)

24.1.2

### Running Jupyter locally or remotely?

Local
Repository: ollama
Issue: Support llama.cpp's Control Vector Functionality
Labels: feature request

llama.cpp added support for control vectors a while ago https://github.com/ggerganov/llama.cpp/pull/5970

They can be loaded via `llama_control_vector_load` and `llama_control_vector_apply` which can take a vector in the form of a `.gguf`

https://github.com/ollama/ollama/blob/main/llama/common.h#L645
https://github.com/ollama/ollama/blob/main/llama/llama.h#L571

Example of how llama.cpp normally applies them: https://github.com/ollama/ollama/blob/main/llama/common.cpp#L920-L944

The vectors can be trained and exported to `.gguf` via https://github.com/vgel/repeng/

It would be great if we could load control vectors the same way that adapter loras can be loaded currently.

```dockerfile
FROM ./models/mistralai/Mistral-7B-Instruct-v0.1
CONTROLVECTOR ./vectors/my_control_vector.gguf 1.5
```

I think this feature would open a range of model customization which is currently only possible through the more difficult (much much slower and way more memory intensive) adaptor training methods
Repository: go
Issue: x/tools/gopls: check CGO_ENABLED when symbol is undefined because of implicit build constraint
Labels: gopls

### Proposal Details

CGO docs says the `import "C"` implies the "cgo" build constraint:

> The go tool will set the build constraint "cgo" if cgo is enabled. The special import "C" implies the "cgo" build constraint, as though the file also said "//go:build cgo". 

Hence, when the code is arranged as this, the `go` tool reports `./main.go:8:6: undefined: sub.API` for the following project in [txtar format](https://pkg.go.dev/golang.org/x/tools/txtar) when I run `CGO_ENABLED=0 go build`. I want to propose this because when a 3rd library uses `import "C"` in a go file with several package level functions and my local `CGO_ENABLED=0`, the build fails without any useful error hint.

The gopls emits the same error hint when the CGO_ENABLED=0.

![image](https://github.com/user-attachments/assets/9791800b-ea72-47d3-8cc8-4f86ba63bfe8)

I proposed the gopls to check the files with `import "C"` additionally after gopls found an `undefined` error from go tool when `CGO` is disabled. It should give an hint that "undefined: sub.API. CGO is disabled so symbols inside file sub.go are excluded" if we can find the symbol API inside file `sub.go`.

This may apply to the undefined symbols which exist in the certain build contraints under the same package. But I would like to narrow the proposal down to CGO only because CGO build constraint is implicit convention but the others are explicit. Moreover, the `import "C"` affects the other functions inside the same file as build contraint is file level.

```
-- go.mod --
module github.com/xieyuschen/example

go 1.21
-- main.go --
package main

import (
	"github.com/xieyuschen/example/sub"
)

func main() {
	sub.API()
}
-- sub/sub.go --
package sub

// int fortytwo()
// {
//	    return 42;
// }
import "C"

func CAPI() {
	C.fortytwo()
}

func API() {
	C.fortytwo()
}
-- sub/sub2.go --
package sub
// this file is used to make a go file available for package sub
```
Repository: godot
Issue: Using constant Typed Dictionary in _export_file in EditorExportPlugin crashes the engine
Labels: bug,topic:gdscript,crash,topic:export

### Tested versions

Does not work in 4.4-dev4, 4.4-dev6

### System information

Godot v4.4.dev6 - Windows 10.0.19045 - Single-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 4050 Laptop GPU (NVIDIA; 32.0.15.6070) - 13th Gen Intel(R) Core(TM) i5-13500HX (20 threads)

### Issue description

Crashes
```gdscript
	func _export_file(path: String, type: String, features: PackedStringArray) -> void:
		const EXCLUDED_DIRECTORIES: Dictionary[String, PackedStringArray] = {
			"testt": [
				"res://testfolder",
			]
		}
	
		for feature: String in features:
			if EXCLUDED_DIRECTORIES.has(feature):
				for directory: String in EXCLUDED_DIRECTORIES[feature]:
					print(path)
					# Skip files inside of this directory
					if path.begins_with(directory): skip()
```

Does not crash (same as above but var instead of const)
```gdscript
	func _export_file(path: String, type: String, features: PackedStringArray) -> void:
		var EXCLUDED_DIRECTORIES: Dictionary[String, PackedStringArray] = {
			"testt": [
				"res://testfolder",
			]
		}
	
		for feature: String in features:
			if EXCLUDED_DIRECTORIES.has(feature):
				for directory: String in EXCLUDED_DIRECTORIES[feature]:
					print(path)
					# Skip files inside of this directory
					if path.begins_with(directory): skip()
```

Does not crash
```gdscript
	func _export_file(path: String, type: String, features: PackedStringArray) -> void:
		const EXCLUDED_DIRECTORIES: Dictionary = {
			"testt": [
				"res://testfolder",
			]
		}
	
		for feature: String in features:
			if EXCLUDED_DIRECTORIES.has(feature):
				for directory: String in EXCLUDED_DIRECTORIES[feature]:
					print(path)
					# Skip files inside of this directory
					if path.begins_with(directory): skip()
```

### Steps to reproduce

Use a Typed dictionary marked with `const` instead of `var` in _export_file of an EditorExportPlugin, then export the project

### Minimal reproduction project (MRP)

[New Compressed (zipped) Folder.zip](https://github.com/user-attachments/files/18145537/New.Compressed.zipped.Folder.zip)
Repository: next.js
Issue: Non-ASCII characters in the slug may cause navigation and routing to break
Labels: Navigation

### Link to the code that reproduces this issue

https://github.com/joulev/debug/tree/nextjs-with-non-ascii-chars

### To Reproduce

Simply start the application in either dev mode or prod mode or on Vercel. Vercel prod mode deployment of the reproduction repo above is already available on https://debug-git-nextjs-with-non-ascii-chars-joulev-proj.vercel.app.

### Current vs. Expected behavior

**Current behaviour**

| | Server `redirect` | Client `router.push` | `next/link` |
|---|---|---|---|
| Local `next dev` | ❌ Error | ❌ 404 | ❌ 404 |
| Local `next start` | ❌ Error | ❌ 404 | ❌ 404 |
| Vercel | ❌ Error | ✅ | ✅ |

**Expected behaviour:** All 9 cases above should work.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 18:51:28 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T8112
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.12.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.0 // Latest available version is detected (15.1.0).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed)

### Additional context

_No response_
Repository: tensorflow
Issue: `tensorflow.experimental.numpy.kron` not working with multidimensional Arrays
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.18

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

2.18.0

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu

### Mobile device

_No response_

### Python version

3.10.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

This is a new issue in replacement for https://github.com/tensorflow/tensorflow/issues/59761 as suggested by @tilakrayal

I tested the function against numpy and it throws an error when the `ndim` of the input tensors is greater than 2.
I run the code on the latest TensorFlow version on PyPI and the nightly version, and I get the same failures.

Also, I am not getting as much debug information only this error

`UnimplementedError: {{function_node __wrapped__Mul_device_/job:localhost/replica:0/task:0/device:CPU:0}} Broadcast between [2,1,5,1,2,1,5,1] and [1,1,1,2,1,3,1,4] is not supported yet. [Op:Mul] name: `

### Standalone code to reproduce the issue

```shell
import tensorflow as tf
import numpy as np
try:
    a = tf.constant(np.arange(100).reshape(2, 5, 2, 5))
    b = tf.constant(np.arange(24).reshape(2, 3, 4))
    print(a.ndim) # 4
    print(b.ndim) # 3

    y = tf.experimental.numpy.kron(a, b)

    print(y.shape)
except:
    print("Can't use tf.experimental.numpy.kron on multi-dimensional arrays")

x = np.arange(100).reshape(2, 5, 2, 5)
y = np.arange(24).reshape(2, 3, 4)

print(x.ndim) # 4
print(y.ndim) # 3

z = np.kron(x, y)

print(z.shape) # (2, 10, 6, 20)
```


### Relevant log output

```shell
UnimplementedError: {{function_node __wrapped__Mul_device_/job:localhost/replica:0/task:0/device:CPU:0}} Broadcast between [2,1,5,1,2,1,5,1] and [1,1,1,2,1,3,1,4] is not supported yet. [Op:Mul] name:
```
Repository: rust
Issue: aarch64-unknown-none-softfloat: ABI unsoundness when enabling "neon" feature
Labels: A-LLVM,T-compiler,I-unsound,I-prioritize,O-AArch64,A-ABI,A-target-feature

Enabling the "neon" target feature on the aarch64-unknown-none-softfloat target is taken by LLVM as a sign that we want to use the hardfloat ABI. That is unfortunate as it makes it UB to link such code against code built for aarch64-unknown-none-softfloat without the "neon" target feature. (Note that it's not "neon" which is problematic but "fp-armv8"; however, the two are tied together by rustc.)

For Rust-generated functions we work around this by forcing our own ABI, passing floats either indirectly or via integer registers (https://github.com/rust-lang/rust/pull/133102). However, this does not help for LLVM-generated calls for builtins/intrinsics, as shown in [this example](https://godbolt.org/z/r56xWo8nT) by @beetrees.

We don't have target maintainers listed for this target, so maybe that means we can just demote it to tier 3? (See https://github.com/rust-lang/rust/issues/113739)

LLVM issue: https://github.com/llvm/llvm-project/issues/110632. So far LLVM maintainers seem to not agree that there is a problem here.

@Amanieu unfortunately your proposal for making floats work on that target doesn't quite suffice. :/ We do need some help from LLVM.
@nikic do you have any good ideas for what we could do here? It seems like rejecting enabling "neon" on aarch64-unknown-none-softfloat is the only sound option we have right now, but I worry that may make the Rust-for-Linux folks (among others) unhappy.
Repository: neovim
Issue: `selection=exclusive` can't select empty region
Labels: needs:vim-patch

### Problem

https://github.com/user-attachments/assets/d2cd0b8b-51fe-4844-9cb8-56c49129463d


### Steps to reproduce

1. prepare files:

`a.txt`

```
(a)
```

`minimal.lua`

```
vim.opt.selection = "exclusive"
```

2. `./nvim.appimage --clean -u minimal.lua a.txt`
3. move cursor on `a`
4. press `vd`
### Expected behavior

delete nothing

### Nvim version (nvim -v)

NVIM v0.11.0-dev-1344+g17383870dd

### Vim (not Nvim) behaves the same?

yes

### Operating system/version

6.12.4-arch1-1

### Terminal name/version

st 0.8.5

### $TERM environment variable

st-256color

### Installation

appimage
Repository: node
Issue: The desiredSize of `Writable.toWeb()` is incorrect
Labels: web streams

### Version

v22.12.0

### Platform

_No response_

### Subsystem

_No response_

### What steps will reproduce the bug?

```ts
import { Writable } from "node:stream";

const nodeWriteable = new Writable({
  write(chunk, encoding, callback) {
    // pending
  },
  highWaterMark: 5,
  objectMode: false,
});
const webWritable = Writable.toWeb(nodeWriteable);
const writer = webWritable.getWriter();
writer.write(new Uint8Array(3));
console.log(nodeWriteable.writableLength, writer.desiredSize); // expect 3,2  actual 0,4

let promise = writer.write(new Uint8Array(3));

console.log(nodeWriteable.writableLength, writer.desiredSize); // expect  6, -1， actual  0,3

```

### How often does it reproduce? Is there a required condition?

always

### What is the expected behavior? Why is that the expected behavior?

I think `writer.desiredSize` should be equal to `highWaterMark - odeWriteable.writableLength`
Otherwise, after the Writable.toWeb() conversion, the buffer queue for the writable stream is expanded

### What do you see instead?

none

### Additional information

_No response_
Repository: ant-design
Issue: Mocky.io/V2 is not found
Labels: help wanted

### Reproduction link

[https://4x.ant.design/components/upload/#header](https://4x.ant.design/components/upload/#header)

### Steps to reproduce

You need to recreate the Mocky API and make sure you set as never expire.

### What is expected?

When i Upload the files the IT SHOULD BE UPLOADED

### What is actually happening?

API response as Not found 400 for the any file upload . 

| Environment | Info |
| --- | --- |
| antd | 4.24.16 |
| React | 17.0.2 |
| System | 23H2 |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: source control
Labels: git


Type: <b>Bug</b>

> Problem Troubleshooting The problem has been determined to be related to Visual Studio Code.
Switch files source control and timeline view to load for a long time
![Image](https://github.com/user-attachments/assets/4f1c733b-93a7-4ab8-b41b-bccc80c85086)



VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Windows_NT x64 10.0.22000
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.78GB (8.12GB free)|
|Process Argv|--log vscode.git=trace --crash-reporter-id 53646982-3320-40cd-b43f-f9bb39c194e6|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (1)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-language-pack-zh-hans|MS-|1.96.2024121109


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

```

</details>

<!-- generated by issue reporter -->
Repository: deno
Issue: lint(no-undef): says `document` is undefined
Labels: bug,lint

Version: Deno 2.1.4

The lint rule `no-undef` https://docs.deno.com/lint/rules/no-undef/ says that it disallows undeclared variables, but I wouldn't expect this to apply to globally available variables like `document`.

### deno.json
```json
{
  "compilerOptions": {
    "lib": ["dom", "dom.iterable", "dom.asynciterable", "deno.ns"]
  },
  "lint": {
    "rules": {
      "include": ["no-undef"]
    }
  }
}
```
### main.ts
```ts
console.log(document);
```
### terminal
```
error[no-undef]: document is not defined
 --> /Users/soul/Projects/lint/main.ts:1:13
  |
1 | console.log(document);
  |             ^^^^^^^^

  docs: https://lint.deno.land/rules/no-undef


Found 1 problem
Checked 1 file
```
Repository: vscode
Issue: Error: EPIPE: broken pipe, write
Labels: bug,upstream,workbench-cli


Type: <b>Bug</b>

using VS Code as Text Editor to Vivado.
Open a   **.v** file in Vivado by VSCode，shows up the error panel below. Click 'yes' or cancel it, then it turns to VSCode and successfully open.

<img width="419" alt="Image" src="https://github.com/user-attachments/assets/db0999ba-5caf-43c1-8a28-5ff9d9a76949" />

Reinstall in another disk didn't help.
How to solve the issue or ignore this error panel and make it directly turn to VSCode?

VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>

<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|13th Gen Intel(R) Core(TM) i9-13900HX (32 x 2419)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.70GB (5.22GB free)|
|Process Argv|E:/download/diglogic-2023/pkg/lab1/multipler/testbench.v -l3 --crash-reporter-id 866be85d-39d2-4bb0-9303-c9db6dd66fb6|
|Screen Reader|no|
|VM|67%|
</details><details><summary>Extensions (14)</summary>

Extension|Author (truncated)|Version
---|---|---
verilog-formatter|Isa|1.0.0
remote-wsl|ms-|0.88.5
cpptools|ms-|1.22.11
veriloghdl|msh|1.15.5
java|red|1.37.0
intellicode-api-usage-examples|Vis|0.2.9
vscodeintellicode|Vis|1.3.2
vscode-gradle|vsc|3.16.4
vscode-java-debug|vsc|0.58.1
vscode-java-dependency|vsc|0.24.1
vscode-java-pack|vsc|0.29.0
vscode-java-test|vsc|0.43.0
vscode-maven|vsc|0.44.0
vim|vsc|1.29.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

```

</details>

<!-- generated by issue reporter -->
Repository: react
Issue: Bug: Scheduler default time interval problem
Labels: Status: Unconfirmed

Hello React Team,

While reviewing the `packages/scheduler/src/SchedulerFeatureFlags.js` file, I noticed that the default frame yield time (`frameYieldMs`) is set to **5 milliseconds**:

```javascript
export const frameYieldMs = 5;
```

I have a few questions regarding this configuration and would appreciate your clarification:

1. Why is 5ms Chosen as the Default Value?
Why not set it to 16.7ms (which corresponds to the 60fps frame rate of most screens) or 50ms (the threshold for long tasks defined by browsers)?
Impact of Frequent Task Interruptions

2. Does setting it to 5ms cause tasks to be interrupted too frequently?
Considering that calling performance.now() itself might take more than 5ms, could this lead to performance overhead?

3. Is This a Bug or an Intended Feature?
Is this setting intentional to optimize specific performance scenarios?
Or could it potentially lead to unintended task interruption issues?

Additional Information
React Version: 17.0.2
Browser Environment: Chrome Version 112.0.5615.49
Steps to Reproduce:
When performing extensive layout computations, I observed that tasks are being frequently interrupted, which results in decreased rendering performance.
Expected Behavior:
The Scheduler should interrupt tasks near the frame time (approximately 16.7ms) to balance rendering performance and responsiveness effectively.
Actual Behavior:
With frameYieldMs set to 5ms, tasks are frequently interrupted, leading to increased scheduling overhead and rendering performance that falls below expectations.

Thank You
Thank you for your hard work and dedication to maintaining React! I look forward to your explanation and any insights you can provide regarding this configuration.
Repository: vscode
Issue: Overtype Mode: backspace should insert spaces in its stead
Labels: feature-request,editor-input

Idea comes from https://github.com/microsoft/vscode/pull/233188

Make regular backspace add spaces in its stead while deleting code in overtype mode. You might also think of this as "destructive" left-arrow.
Repository: angular
Issue: Suggestion: Integrate defer and Resource APIs for Seamless Asynchronous State Handling
Labels: area: core,core: reactivity,cross-cutting: signals,core: defer

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

_No response_

### Description

With the introduction of the `defer` and the `Resource` API in Angular 19, developers now have powerful tools to handle asynchronous data more declaratively in their applications. Both APIs support states like `loading`, `resolved`, and `error`, which are critical for managing async workflows in the UI.  

However, these two features currently work independently. It seems like a natural fit for `defer` and `Resource` to work together, leveraging their respective strengths to simplify and enhance the developer experience for handling asynchronous data.  

### Proposed solution

Introduce an integration between the `defer` and the `Resource` API to enable seamless usage in templates. Possible features could include:  

1. Allowing `defer` to accept a `Resource` as its input, automatically binding to its state transitions (`loading`, `resolved`, `error`).  
2. Providing built-in optimizations for rendering `Resource` states declaratively with `defer`. For example, a `Resource`-aware `defer` could simplify boilerplate code for displaying loading spinners, error messages, or resolved data.  
3. Ensuring consistent state management and declarative workflows across the framework when combining these APIs.  

### Alternatives considered

- **Manual Handling:** Developers can currently use `defer` and `Resource` separately, manually binding their states to templates. While functional, this requires additional boilerplate and lacks the declarative synergy that integration could provide.  
- **Custom Wrappers:** Developers can write custom helper to bridge `defer` and `Resource`, but this approach increases complexity and reduces framework-wide consistency.  
- **Leave as Is:** The features can remain independent, but integration would better align with Angular’s goal of reducing friction in building modern web applications.  

This proposed integration would streamline how developers handle asynchronous data, making Angular more intuitive and powerful for real-world use cases.