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,154 public repositories matching this topic...

next.js
leerob
leerob commented Jul 9, 2021

Describe the feature you'd like to request

These are common issues developers run into with Next.js. Some are mentioned in the docs, but ideally you don't have to go check the docs.

Describe the solution you'd like

Instead, ESLint can provide compile-time feedback and suggestions.

  • Trying to call an API route from inside getStaticProps / getServerSideProps leading to [next build

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 Oct 28, 2021
  • JavaScript
svelte
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

assemblyscript
Nim
youknowone
youknowone commented Oct 16, 2021

For now, Object protocol methods are (mostly) thin wrapper of matching vm functions. Because we don't need to have duplicated functions for same features, they need to be moved from vm to object protocol functions.

  • vm path: vm/src/vm.rs
  • object protocol path: vm/src/protocol/object.rs

The matching vm functions are easy to find because object methods are calling it.

  • get_att
numba
juliusbierk
juliusbierk commented Oct 19, 2021

I believe this is undocumented behaviour.

import numba as nb


@nb.njit
def f1():
    for i in nb.prange(1):
        print(type(i))  # >>> int64


@nb.njit(parallel=True)
def f2():
    for i in nb.prange(1):
        print(type(i))  # >>> uint64


f1()
f2()

This caused a nasty bug in my own code that was hard to debug as the problem did not exist without `parallel=Tr