Skip to content
#

Compiler

Compilers are software that translate higher-level (more human readable) programming languages to lower-level languages (e.g. machine code). The processor executes machine code, which indicates when binary high and low signals are required in the arithmetic logic unit of the processor. Examples of compiled languages include BASIC, Fortran, C++, C, and Java.

Here are 6,895 public repositories matching this topic...

next.js
w4-hanggi
w4-hanggi commented Mar 11, 2022

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Binaries:
  Node: 16.14.0
  npm: 8.3.1
  Yarn: 1.22.17
  pnpm: 6.32.
good first issue area: examples

A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

  • Updated Apr 8, 2022
  • JavaScript
svelte
ehsan2003
ehsan2003 commented Feb 7, 2022

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

feature request good first issue docs
Joe-Edwards
Joe-Edwards commented Apr 7, 2022

Preliminary Checks

Description

type: bug help wanted good first issue topic: source-plugins
dtzxporter
dtzxporter commented Oct 7, 2021

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

good first issue category: ESM
mischnic
mischnic commented Mar 29, 2022

It would be great if you could try to use the same/compatible dependency version across the swc crates, for example:

[[package]]
name = "swc_cached"
version = "0.1.1"
dependencies = [
 ...
 "dashmap 5.2.0",
]

[[package]]
name = "swc_ecma_loader"
version = "0.29.0"
dependencies = [
 ...
 "dashmap 4.0.2",
]

[[package]]
name = "swc_ecma_transforms_react"
version = "0.100
assemblyscript
Nim
MichalMarsalek
MichalMarsalek commented Dec 16, 2021

On Windows, when stack size limit is exceeded, the program ends with "Error: execution of an external program failed" with no details provided. For noobies like me, it might be helpful if the compiler gives some indication of why that is.

The simplest would be to create a warning when a single large array is defined in the code.
More advanced solution would take the combined the sizes of diffe

loic-joly-sonarsource
loic-joly-sonarsource commented Mar 15, 2022

Is your feature request related to a problem? Please describe

Very often, with working with conformance view, I work with different versions of the same compiler, all options are the same. Or I work with different C++ standards, with the same compiler and the same options (exception for this one). Or...

Right now, to add a new compiler in the conformance view, I have to start from an empty

ui good first issue request
numba
rhjmoore
rhjmoore commented Sep 1, 2021

I see comments suggesting adding this to understand how loops are being handled by numba, and in the their own FAQ (https://numba.pydata.org/numba-doc/latest/user/faq.html)

from llvmlite import binding as llvm
llvm.set_option('','--debug-only=loop-vectorize')

You would then create your njit function and run it, and I believe the idea is that it prints debug information about whether

good first issue bug - documentation incorrect