This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-30
Channels
- # announcements (7)
- # beginners (103)
- # boot (62)
- # cider (14)
- # clara (10)
- # cljdoc (4)
- # cljs-dev (2)
- # cljsrn (2)
- # clojure (51)
- # clojure-dev (15)
- # clojure-europe (13)
- # clojure-italy (25)
- # clojure-japan (3)
- # clojure-nl (4)
- # clojure-spec (6)
- # clojure-uk (9)
- # clojurescript (72)
- # clojureverse-ops (2)
- # community-development (2)
- # core-async (35)
- # cursive (16)
- # datascript (1)
- # datomic (12)
- # duct (2)
- # emacs (2)
- # fulcro (9)
- # graphql (5)
- # hoplon (5)
- # leiningen (3)
- # luminus (1)
- # nyc (1)
- # off-topic (41)
- # other-languages (1)
- # pathom (16)
- # pedestal (2)
- # re-frame (44)
- # reitit (1)
- # shadow-cljs (33)
- # spacemacs (12)
- # test-check (9)
- # tools-deps (15)
- # vim (4)
Any Pythonistas here, what's your property testing library of choice? (Looking for test.check or quickcheck like library not necessarily spec)
@jaihindhreddy I used https://hypothesis.readthedocs.io/en/latest/ to good effect. Quite pleasant to use too.
what would be a good name for the expressions x y z (bar 1 2 3)
in (foo x y z (bar 1 2 3)
?
I want to come up with a name to skip linting arguments to function calls, so you can say donât lint arguments to foo.
the reason is that foo can be a macro which rewrites expressions which gives false positives
names Iâve already considered:
:disable-within
, :skip-calls
, :skip-args
, :not-inside
, but it all doesnât feel satisfying
note that not the entire (foo ...)
expression is skipped, just the linting of the arguments
@borkdude :whitelisted-args
or :unchecked-args
like *unchecked-math*
?
what feels wrong to me about args
is that (bar 1 2 3)
doesnât feel like an âargâ, but I guess thatâs how they call it
im thinking in terms of turn a blind eye towards these args
eastwood has this: https://github.com/jonase/eastwood/blob/master/resource/eastwood/config/clojure.clj#L7
but to the consumer of the API it could be unnecessary impl details?
@rahul080327 yes, thatâs why I donât prefer children
somehow I'm more drawn towards names like unsafe { }
blocks or native { }
wherein we are saying I know what Im doing here
hence the use of unchecked
IMO
well, here itâs more like: the linter is almost surely wrong, but you might also still be đ
I already have :skip-comments
, so for consistency it may make sense to keep the word skip
but then again, skip-comments
can now be configured yourself as :skip-args [clojure.core/comment]
, so Iâm not sure if that one stays⊠đ
(and if anyone genuinely wants to discuss Slack alternatives, we have #community-development for that)
I think I ran into some issue of the font conflict, but I don't known which font is conflict with the font awesome font(which I used to display icons in status bar)
are you on fedora? the packaged font awesome (5, I believe) was known to have this sort of problem. There should be chatter around the issue involving "i3wm" and the like. I was never quite able to solve it and just removed FA icons from my jaybar
@dougkrieger thanks for the reply. I'm on the manjaro(arch linux), use xfce as desktop.
I think maybe they are the same. don't know how unicode is displayed. when you install FA, you don't have to use FA as the font, you can use any font but the unicode will be displayed according to the FA.
I vaguely remember the issue being some pre-packaged font patched with FA overriding the "real" FA
not sure how helpful this is @doglooksgood but there is a command to search fonts by aliases, and if you search "FontAwesome" or the like you might be able to find the culprit (i.e. the alias will resolve to the troublesome patched font)