Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
hashseed's profile
Yang Guo
Yang Guo
Yang Guo
@hashseed

Tweets

Yang Guo

@hashseed

living documentation for many parts of @v8js

github.com/hashseed
Joined April 2014

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. KΞNNΞTH C. in Paris (#w3cTAG meeting) 🇫🇷‏ @kennethrohde Oct 10
      Replying to @justinfagnani

      cc/ @littledan

      1 reply 0 retweets 0 likes
    2. Daniel Ehrenberg‏ @littledan Oct 11
      Replying to @kennethrohde @justinfagnani

      Hmm, I can definitely see the value in this, but I'm also concerned about the overhead of doing it for every function invocation, and not sure what the interface for accessing it should be. I've been wondering whether we should include a handle in decorators for object literals.

      1 reply 0 retweets 1 like
    3. Justin Fagnani‏ @justinfagnani Oct 11
      Replying to @littledan @kennethrohde

      Could the handle just be generated on demand? It's similar to getting the just second to last frame on the call stack, yeah?

      1 reply 0 retweets 1 like
    4. Daniel Ehrenberg‏ @littledan Oct 11
      Replying to @justinfagnani @kennethrohde

      I dunno, maybe depends on the details of the API surface. It's hard for me to think of one that would lend itself to that.

      2 replies 0 retweets 1 like
    5. Daniel Ehrenberg‏ @littledan Oct 11
      Replying to @littledan @justinfagnani @kennethrohde

      cc @hashseed who knows much much more about what kinds of things are possible here with respect to low-overhead debugging interfaces than me.

      1 reply 0 retweets 1 like
    6. Yang Guo‏ @hashseed Oct 11
      Replying to @littledan @justinfagnani @kennethrohde

      What do you exactly mean with "handle". JS does not have a concept of call site so far, except for the unspec'ed Error.stack. How would you expect it to be exposed? As a string describing the source location?

      1 reply 0 retweets 0 likes
    7. Justin Fagnani‏ @justinfagnani Oct 11
      Replying to @hashseed @littledan @kennethrohde

      I mean an opaque object unique per callsite. More like a Symbol than a string. It would only useful as a key for maps, or for host integration like Jump to Source in dev tools.

      1 reply 0 retweets 0 likes
    8. Justin Fagnani‏ @justinfagnani Oct 11
      Replying to @justinfagnani @hashseed and

      Imagine a rough "polyfill": let callsites = new WeakMap(); let callsite = (s) => { let cs = callsites.get(s); if (cs === undefined) { callsites.set(s, cs = Symbol()) } return cs; } And transform: f() to very-roughly: f(callsite``)

      1 reply 0 retweets 0 likes
    9. Yang Guo‏ @hashseed Oct 11
      Replying to @justinfagnani @littledan @kennethrohde

      So iiuc you are interested in the source location of the call? Disregarding how call sites are represented, finding it on-demand should be easy by just waking the stack and not have runtime overhead. Not sure about security implications though.

      1 reply 0 retweets 2 likes
    10. Justin Fagnani‏ @justinfagnani Oct 11
      Replying to @hashseed @littledan @kennethrohde

      Yep, but I don't care about understanding the source location object. Security may be helped by the handle being opaque (can't report to a server who's calling you) and the fact that a function should only ever generate a callsite source location for itself.

      1 reply 0 retweets 1 like
      Yang Guo‏ @hashseed Oct 12
      Replying to @justinfagnani @littledan @kennethrohde

      What's your use case? Just to distinguish call sites for the same function?

      1:52 PM - 12 Oct 2018
      • 1 Like
      • KΞNNΞTH C. in Paris (#w3cTAG meeting)🇫🇷
      1 reply 0 retweets 1 like
        1. New conversation
        2. Justin Fagnani‏ @justinfagnani Oct 12
          Replying to @hashseed @littledan @kennethrohde

          Yeah. Think of JSX / VDOM. You have a deeply nested call hierarchy that represents some state kept elsewhere. You invoke this repeatedly over time to get the new state, but sometimes you need to access the old state. Keying that old state by source location would work perfectly.

          1 reply 0 retweets 1 like
        3. Yang Guo‏ @hashseed Oct 12
          Replying to @justinfagnani @littledan @kennethrohde

          Not sure that's a common use case to justify as language feature, but for sure not too hard to implement without runtime overhead.

          1 reply 0 retweets 1 like
        4. Justin Fagnani‏ @justinfagnani Oct 12
          Replying to @hashseed @littledan @kennethrohde

          VDOM is extremely common though, and if it could more easily reconcile without the diff a significant amount of the web could benefit.

          1 reply 0 retweets 2 likes
        5. Daniel Ehrenberg‏ @littledan Oct 12
          Replying to @justinfagnani @hashseed @kennethrohde

          I wonder if there's a good way this could be experimented with in tooling, before putting it as a built-in feature. Some horrible hack with error stacks, looking at the top two entries???

          1 reply 0 retweets 1 like
        6. Justin Fagnani‏ @justinfagnani Oct 25
          Replying to @littledan @hashseed @kennethrohde

          Pinging here, because the new React Hooks feature is trying to tie a callsite to a state object almost exactly like my use case, and accomplishes it in the same hacky way that I considered: keep a stack of invocations and disallow conditionals.https://reactjs.org/docs/hooks-intro.html …

          0 replies 0 retweets 2 likes
        7. End of conversation

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2018 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Cookies
        • Ads info