Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Home
Binaries:
Node: 16.13.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant packages:
next: 12.1.7-canary.19
react: 18.1.0
react-

Describe the problem

the low level documentation (https://svelte.dev/docs) is not really easy to use ( and incomplete in some cases)
I think if the runtime function contain JSDOC it will help a lot and give the developers an easier way to discover api documentation

additionally it is possible to replace the https://svelte.dev/docs with the generated docs ( with some thing like https://ty

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

I'v

💻

• Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

visitors: {
    JSXElement(path) {
        console.log(path.generateUidIdentifierBasedOnNode(path.node));
        // logs `_objectObject`
    }
}

Configuration file name

No response

Configuration

No response

Current and expected behavior

Logs

🐛 bug report

Parcel (resp. PostHTML) deletes PHP tags from HTML input files during transformation. It also ignores any directives options in .posthtmlrc that are supposed to preserve them.

🎛 Configuration

Minimal default configuration, see below.

🤔 Expected Behavior

The resulting file should contain all <?= ... ?> and <?php ... ?> tags in the input file as-is.

Marked version:
3.x.x

Describe the bug
A clear and concise description of what the bug is.

Right now, import {use} from "markedjs" does not work, this worked in 2.x.x.

To Reproduce
Steps to reproduce the behavior:

Install & import it.
The DefinitelyTyped definitions also mark this incorrectly as being supported still.

A workaround is importing one of the structur

I think the Carbon project would welcome a proposal to add an explicit syntax that forces a tail call. This is aligned with our goals of predictable performance and giving the user explicit control.

My syntax suggestion: tail return F(...);.

Background:

• [[[clang::musttail]] attribute for guaranteed tail calls.](https://reviews.llvm.org/D9951

Describe the feature

Related with swc-project/swc#3859.

We want to establish initial feature parity to existing @swc/cli to plan out migration with possible breaking changes.

These are initial flags we'd like to have.

• config
• config_file
• filename (swc-project/swc#4016)
• env_name
• ignore

Example:

function foo<TArr extends ArrayLike<number>>(arr: TArr): valueof<TArr> {
    type T = valueof<TArr>; // doesn't work yet "ERROR AS100: Not implemented: Inner type alias"
    let element: T = arr[0];
    return element;
}

I was casually trying out Nim-lang and playing with nimpretty. Ofcourse I decided to mess with a flag called "indent", and nimpretty doesn't seem to handle this.

I don't really have the time to do a full bisect, I just installed it and played around. Felt it was better to report this than to ignore it.

Example run

 ~ :: nim r a.nim
Hint: used config file '/etc/nim/nim.cfg' [Conf]
H

Feature

_winapi.GetModuleFileName

Python Source code

https://github.com/python/cpython/blob/v3.10.5/Modules/_winapi.c#L1292-L1324

Describe the bug

See example here

When the flag -flto is given to add link-time optimization, it seems that (at least for g++ and clang++; I have not tested others), the output of the assembly changes to something which is not legible.

Steps to reproduce

1. Visit godbolt.org
2. Create some C++ script
3. Add a compiler window.

• When compilin

• I have tried using the latest released version of Numba (most recent is
  visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
• I have included a self contained code sample to reproduce the problem.
  i.e. it's possible to run as 'python bug.py'.

I think I have discovered a very minor bug - or rather inconsistency with numpy - in Numba's implementation