Main

related bits

0

processing priority

4

site type

0 (generic, awaiting analysis)

review version

11

html import

20 (imported)

Events

first seen date

2024-03-04 13:06:45

expired found date

-

created at

2024-06-04 21:12:19

updated at

2025-12-28 01:46:04

Domain name statistics

length

13

crc

17123

tld

2211

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

-

previous id

0

replaced with id

0

related id

-

dns primary id

57766531

dns alternative id

0

lifecycle status

0 (unclassified, or currently active)

Subdomains and pages

deleted subdomains

0

page imported products

0

page imported random

0

page imported parking

0

Error counters

count skipped due to recent timeouts on the same server IP

0

count content received but rejected due to 11-799

0

count dns errors

0

count cert errors

0

count timeouts

0

count http 429

0

count http 404

0

count http 403

0

count http 5xx

0

next operation date

-

Server

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

97415

mp size raw text

16843

mp inner links count

16

mp inner links status

20 (imported)

Open Graph

title

Yonas Kolb

description

image

site name

Yonas Kolb

author

updated

2025-12-15 16:10:08

raw text

Yonas Kolb Yonas Kolb Swift 3 Set insert behaviour June 30, 2016 by Yonas Kolb I was updating some code from 2.2 to 3 today and came across some unexpected behaviour in code that was inserting values into a Set. I was using insert(_ newMember: Element) to basically update a value that was already stored in the Set. When upgrading to swift 3, calling this function didn't update the value that was stored anymore and simply did nothing. A look through the API docs revealed a new function called update(with newMember:Element) that behaves like the old insert - adds an element to the Set if not present, otherwise updates the element. Replacing the old insert with update manually fixed the problem. I couldn't find anything online mentioning this change in behaviour, so I imagine many developers out there may not be aware of it. The Swift 3 migrator should perhaps replace any insert calls with update so there are no unintended consequences in places that rely on the ol...

Text analysis

redirect type

0 (-)

block type

0 (no issues)

detected language

1 (English)

category id

Sprzęt mobilny (205)

index version

2025110801

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

12877

text words

2731

text unique words

880

text lines

362

text sentences

118

text paragraphs

35

text words per sentence

23

text matched phrases

1

text matched dictionaries

1

RSS

rss path

rss status

3 (priority 3 already searched, no matches found)

rss found date

-

rss size orig

0

rss items

0

rss spam phrases

0

rss detected language

0 (awaiting analysis)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap path

sitemap status

1 (priority 1 already searched, no matches found)

sitemap review version

1

sitemap urls count

0

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

0

sitemap found date

-

sitemap process date

-

sitemap first import date

-

sitemap last import date

-