DataScript 0.9.0 demonstration of possible bug in entity-ID generation when creating new component entities within transaction

gistfile1.clj

(ns demo.main
  (:require [datascript :as ds]))

(def schema
  {:x/component {:db/valueType :db.type/ref ; Required to demonstrate bug.
                 :db/isComponent true ; Required to demonstrate bug.
                 :db/cardinality :db.cardinality/many
                   ; Not required but demonstrates what happens to ID numbering
                   ; after first component.
                 }})

(def conn
  (ds/create-conn schema))

(ds/transact! conn
  [{:x/component [{:c/attribute "blah"} {:c/attribute "bar"}]}
   {:y/completely-different "foo"}])

(enable-console-print!)
(prn @conn)

; Will print something like:
; #datascript/DB {:schema ...
;                 :datoms [[1 :c/attribute "blah" 536870913]
;                          [1 :x/component 1 536870913]
;                          [1 :x/component 2 536870913]
;                          [2 :c/attribute "bar" 536870913]
;                          [3 :y/completely-different "foo" 536870913]]}

; The IDs of the new components of the first entity (i.e., values of [1 :x/component _]) are 1 and 2,
; referring to the non-component entities created in the same transaction, rather than separate
; component entities. In particular, the [1 :x/component 1] is an unexpected circular reference.
; (The circular reference from 1 to 1 causes an infinite loop when coupled with another bug
; when using the Push API on entity 1.)