Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get rid of warnings during compilation #25

Open
smoes opened this issue Sep 11, 2019 · 2 comments
Open

Get rid of warnings during compilation #25

smoes opened this issue Sep 11, 2019 · 2 comments
Assignees

Comments

@smoes
Copy link
Contributor

smoes commented Sep 11, 2019

When compiling the project, the following warnings are shown. We should get rid of these to have clean build output.

[Figwheel:WARNING] Compile Warning   /home/simon/git/active-clojure/test/active/clojure/record_test.cljc   line:272  column:1

  map->GenerativeRecord at line 261 is being replaced

  267  ;;; After evaluating the following expression, it is expected, that you get warnings like these
  268  ;; [Figwheel:WARNING] Compile Warning: map->GenerativeRecord at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  269  ;; [Figwheel:WARNING] Compile Warning: generative-record? at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  270  ;; [Figwheel:WARNING] Compile Warning: make-generative-record at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  271  
  272  (define-record-type GenerativeRecord
       ^---
  273     (make-generative-record)
  274     generative-record?
  275     [])
  276  
  277  ;;; Nongenerative

[Figwheel:WARNING] Compile Warning   /home/simon/git/active-clojure/test/active/clojure/record_test.cljc   line:272  column:1

  generative-record? at line 261 is being replaced

  267  ;;; After evaluating the following expression, it is expected, that you get warnings like these
  268  ;; [Figwheel:WARNING] Compile Warning: map->GenerativeRecord at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  269  ;; [Figwheel:WARNING] Compile Warning: generative-record? at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  270  ;; [Figwheel:WARNING] Compile Warning: make-generative-record at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  271  
  272  (define-record-type GenerativeRecord
       ^---
  273     (make-generative-record)
  274     generative-record?
  275     [])
  276  
  277  ;;; Nongenerative

[Figwheel:WARNING] Compile Warning   /home/simon/git/active-clojure/test/active/clojure/record_test.cljc   line:272  column:1

  make-generative-record at line 261 is being replaced

  267  ;;; After evaluating the following expression, it is expected, that you get warnings like these
  268  ;; [Figwheel:WARNING] Compile Warning: map->GenerativeRecord at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  269  ;; [Figwheel:WARNING] Compile Warning: generative-record? at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  270  ;; [Figwheel:WARNING] Compile Warning: make-generative-record at line 212 is being replaced  /Users/kaan/projekte/active-clojure/test/active/clojure/record_test.cljc   line:217  column:1
  271  
  272  (define-record-type GenerativeRecord
       ^---
  273     (make-generative-record)
  274     generative-record?
  275     [])
  276  
  277  ;;; Nongenerative
@neshtea
Copy link
Member

neshtea commented Jan 19, 2023

Is this still an issue, @smoes @kaaninho? I have not encountered this in a while. If this has been fixed, please close this.

@kaaninho
Copy link
Contributor

kaaninho commented Jan 20, 2023

I can't reproduce it either, but didn't do anything that could've fixed it. @smoes ?

Edit: I just saw it again, so this issue still remains.

@kaaninho kaaninho assigned smoes and unassigned kaaninho Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants