-
```
ts=2024-07-01T08:40:22.020Z caller=main.go:87 level=info msg="Starting blackbox_exporter" version="(version=0.25.0, branch=HEAD, revision=ef3ff4fef195333fb8ee0039fb487b2f5007908f)"
7์ 01 17:40:โฆ
-
```ts
export const foo: IO = () => "hello";
// These assignments compile because the types are compatible, but the semantics are such that doing so is almost certainly an error.
export const bar:โฆ
-
There are a few gotchas around tree shaking, so it would be useful to document these somewhere. This applies to other libraries in the fp-ts ecosystem, such as monocle-ts.
Below is my understandingโฆ
-
# ๐ Bug report
**see repo**
https://github.com/alexn-s/pkg-fp-ts-error
## problem
package a node js into a binary with pkg (by vercel) which use fp-ts Either results in an error at runtiโฆ
-
I stumbled across this several times and maybe it has been discussed as well. How to name qualified imports in the fp-ts ecosystem?
## Situation in PureScript/Haskell
In languages like Haskell oโฆ
-
## ๐ Bug report
### Current Behavior
When I add package.json in my submodules with the same version of io-ts and fp-ts I get errors with type inferences resolution that I can't comprehend.
##โฆ
-
## ๐ Feature request
### Current Behavior
When an exception happens inside of an operator, the stack trace is ambiguous: it does not say which operator the exception occurred inside of.
```tsโฆ
-
I got '.clang-format' at project root, system root, every root you can image :)
What ever I try, never get '.clang-format' working. LSP-clangd never respects styles from this file.
Also `clangd.fโฆ
-
# fp-ts๋ก Typescript ํจ์ํ ํ๋ก๊ทธ๋๋ฐ ์์ํ๊ธฐ 3 (Semigroup) | Minsu's Dev Log
๋ณธ ํฌ์คํธ๋ fp-ts ๊ณต์ ๋ฌธ์์ Learning Resources์ ์๋ Getting Started์์ ์๊ฐํ๋ ๋ฌธ์๋ค์ ๋ฒ์ญํ๋ฉฐ ํ์ตํ ๋ฌธ์์
๋๋ค. ์๋ณธ ๋ฌธ์๋ ๋งํฌ์์ ํ์ธํ ์ ์์ผ๋ฉฐ ์์ฑํ ์ฝ๋๋ค์ ์ฌ๊ธฐ์์ ํ์ธํ ์ ์์ต๋โฆ
-
The following is a bit tedious, if not confusing to read:
```ts
import { option, array } from 'fp-ts'
const f = array.array.sequence(option.option)
```
Adding something like the following (to eโฆ